From: Chip Salzenberg <chip@pobox.com>
To: Frans Pop <aragorn@tiscali.nl>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net, 165744@bugs.debian.org
Subject: Re: Debian bug #165744 - 'Received erroneous SM_UNMON request'
Date: Sun, 14 Sep 2003 22:23:03 -0400 [thread overview]
Message-ID: <20030915022303.GB8188@perlsupport.com> (raw)
In-Reply-To: <200309132202.47195.aragorn@tiscali.nl>
According to Frans Pop:
> In monitor.c there is the statement
> my_name = "127.0.0.1"
> when servicing SM_MON requests with secure-statd enabled.
> I think in my setup this causes the lookups in the run-time list (which use
> my_name) to fail when servicing SM_UNMON requests if in my situation my_name
> is equal to the real adresses of my boxes, causing the 'Received erroneous
> SM_UNMON request' errors.
Interesting!
Neil, I'd seen the assignment to my_name but I figured it was just a
housekeeping variable for connections. But if it's used in a later
lookup, assigning to my_name could be a Bad Thing. I'm not sure
enough of my understanding of statd to answer this suggestion.
> I think this would also explain the 'notify_host: failed to notify 127.0.0.1'
> errors. This second error occurs when I reboot the server while a
> NFS-connection was up: after restarting the server tries to notify the client
> it is back up, but can't because the client is not at localhost but at
> 10.19.66.21 and there is no NFS-client running on the server itself.
You've lost me.
> I think the reason the error appears in my setup could be because I have NFS
> kernel-support compiled in both server and clients. In Debian, this means
> rpc.lockd is not run from the init scripts.
What does the timing of lockd have to do with it? Because that's the
only difference between a user-space lockd and a kernel-thread lockd;
the kernel thread only starts up when something might need it, while
the user-space one starts up at boot time.
--
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:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-09-15 2:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 20:02 Debian bug #165744 - 'Received erroneous SM_UNMON request' Frans Pop
2003-09-15 2:23 ` Chip Salzenberg [this message]
2003-09-15 16:46 ` Frans Pop
2003-09-22 3:24 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
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-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
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=20030915022303.GB8188@perlsupport.com \
--to=chip@pobox.com \
--cc=165744@bugs.debian.org \
--cc=aragorn@tiscali.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox