From: "JaniD++" <djani22@dynamicweb.hu>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file
Date: Sat, 3 Dec 2005 14:00:52 +0100 [thread overview]
Message-ID: <00e501c5f809$99c70bc0$0400a8c0@dcccs> (raw)
In-Reply-To: 1133481721.9597.37.camel@lade.trondhjem.org
Hi,
----- Original Message -----
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, December 02, 2005 1:02 AM
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file
> On Thu, 2005-12-01 at 23:47 +0100, JaniD++ wrote:
> > Hello, list,
> >
> > I get this after upgrade from 2.6.14.2
> >
> > [root@dy-xeon-1 etc]# adduser someuser
> > adduser: unable to lock password file
> > [root@dy-xeon-1 etc]#
> >
> > I use nfsroot!
>
> I'm seeing no trouble with locking on 2.6.15-rc3 (with or without the
> -onolock option). Could you please use 'strace' to get a dump of what
> adduser is failing on?
Here is the strace-s output: (20KB)
http://download.netcenter.hu/bughunt/20051203/adduser.log
This problem is always on on 2.6.15-rc3, and newer on 2.6.14.2
Cheers,
Janos
>
> Cheers,
> Trond
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-12-03 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 22:47 2.6.15-rc3: adduser: unable to lock password file JaniD++
2005-12-02 0:02 ` Trond Myklebust
2005-12-02 10:55 ` JaniD++
2005-12-02 11:08 ` Marc Koschewski
2005-12-02 11:26 ` JaniD++
2005-12-03 13:00 ` JaniD++ [this message]
2005-12-03 15:11 ` Trond Myklebust
2005-12-04 14:45 ` JaniD++
2005-12-04 14:53 ` Trond Myklebust
2005-12-05 23:14 ` JaniD++
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00e501c5f809$99c70bc0$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox