From: Chip Salzenberg <chip@debian.org>
To: Jordi Mallach <jordi@debian.org>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net, 203918-quiet@bugs.debian.org
Subject: Re: [chip@debian.org: Debian Bug#203918 - statd request on eth interface, not localhost?]
Date: Wed, 20 Aug 2003 13:59:51 -0400 [thread overview]
Message-ID: <20030820175951.GB3639@perlsupport.com> (raw)
In-Reply-To: <20030813082216.GA14015@nubol.int.oskuro.net>
According to Jordi Mallach:
> I told Chip I'd try to upgrade to the latest 2.6.0 kernel soon. If this
> makes it improve, I'll tell you.
So, what news?
If you're still getting invalid statd requests from an IP other than
127.0.0.1, they're not from the kernel. Can you use tcpdump to find
out where the statd requests are coming from?
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-08-21 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 15:21 [chip@debian.org: Debian Bug#203918 - statd request on eth interface, not localhost?] Chip Salzenberg
2003-08-13 4:06 ` Neil Brown
2003-08-13 8:22 ` Jordi Mallach
2003-08-20 17:59 ` Chip Salzenberg [this message]
2003-08-21 7:58 ` Jordi Mallach
2003-08-21 14:48 ` Chip Salzenberg
2003-08-22 19:38 ` Jordi Mallach
2003-08-20 18:06 ` Debian bug #165744 - 'Received erroneous SM_UNMON request' Chip Salzenberg
2003-08-22 6:26 ` Neil Brown
2003-08-22 15:10 ` Chip Salzenberg
2003-08-25 6:37 ` Neil Brown
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=20030820175951.GB3639@perlsupport.com \
--to=chip@debian.org \
--cc=203918-quiet@bugs.debian.org \
--cc=jordi@debian.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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.