From: Marc Koschewski <marc@osknowledge.org>
To: JaniD++ <djani22@dynamicweb.hu>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file
Date: Fri, 2 Dec 2005 12:08:07 +0100 [thread overview]
Message-ID: <20051202110805.GA7224@stiffy.osknowledge.org> (raw)
In-Reply-To: <00f801c5f72e$df2e58c0$0400a8c0@dcccs>
* JaniD++ <djani22@dynamicweb.hu> [2005-12-02 11:55:09 +0100]:
> 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?
>
> OK, i will try it, if i can.... (this is a productive online system, maybe
> next reboot)
I'd rather suggest to _not_ run -rc kernels on productive systems. :)
Marc
next prev parent reply other threads:[~2005-12-02 11:09 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 [this message]
2005-12-02 11:26 ` JaniD++
2005-12-03 13:00 ` JaniD++
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=20051202110805.GA7224@stiffy.osknowledge.org \
--to=marc@osknowledge.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.