All of lore.kernel.org
 help / color / mirror / Atom feed
From: "JaniD++" <djani22@dynamicweb.hu>
To: "Marc Koschewski" <marc@osknowledge.org>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file
Date: Fri, 2 Dec 2005 12:26:34 +0100	[thread overview]
Message-ID: <011401c5f733$46a3cd60$0400a8c0@dcccs> (raw)
In-Reply-To: 20051202110805.GA7224@stiffy.osknowledge.org

Hi,

> > 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. :)

Thanks for the warning! :-)

I know it, already.
But have no choice. :(
The older kernels didnt know what i have needed! :-/

eg: i try the 2.6.15-rc3 because 2.6.14.2 gives me this messages:

KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
nfs: server 192.168.2.100 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK
nfs: server 192.168.2.100 OK

So, i really did not see different! :-D

Cheers,

Janos

>
> Marc


  reply	other threads:[~2005-12-02 11:31 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++ [this message]
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='011401c5f733$46a3cd60$0400a8c0@dcccs' \
    --to=djani22@dynamicweb.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@osknowledge.org \
    --cc=netdev@vger.kernel.org \
    /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.