All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lawrence Ong <lawrence.ong@netregistry.com.au>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: SM_UNMON again -> kernel
Date: Sun, 13 Jul 2003 14:25:57 +1000	[thread overview]
Message-ID: <20030713042557.GA12903@quasar.nro.au.com> (raw)
In-Reply-To: <shsr84x768e.fsf@charged.uio.no>

On Fri, Jul 11, 2003 at 11:38:57AM +02i0, Trond Myklebust wrote:
> 
> Is /etc/hosts consistent? The kernel only sends MON/UNMON requests on
> the loopback port, so this suggests that something is translating
> 127.0.0.1<->"mymachine" instead of to "localhost".

Consistent?

Well, this is what i have in /etc/hosts

127.0.0.1 localhost
10.1.1.180 mymachine

With some knowledge looking at the monitor.c code, when i changed my
/etc/hosts to:

127.0.0.1 localhost mymachine

The erroneous error disappeared.  Dont't think this should be happening
AT ALL.  The statd code section:

/* Match! */
dprintf(L_DEBUG, "UNMONITORING %s for %s",
		mon_name, my_name);

Is entered when i changed /etc/hosts to 127.0.0.1 localhost mymachine.
Then again, it's logical since my_name in statd's code is set to
127.0.0.1 automatically due to CERT CA-99.05.  Maybe it's got to be
rewritten somewhat?

Anyhow, it shows that the kernel is still continually sending out
unmonitor packets to statd at regular intervals.  What the?  Why is
this happening?

Thanks for the help.

Cheers,
Lawrence

> 
> Cheers,
>   Trond


-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2003-07-13 23:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11  6:16 SM_UNMON again -> kernel Lawrence Ong
2003-07-11  9:38 ` Trond Myklebust
2003-07-13  3:22   ` Philippe Troin
2003-07-13 15:25     ` Trond Myklebust
2003-07-13 18:00       ` Philippe Troin
2003-07-13 23:36         ` Lawrence Ong
2003-07-14  8:56         ` Trond Myklebust
2003-07-18  1:08           ` Philippe Troin
2003-07-19  3:26             ` Philippe Troin
2003-07-19 16:22               ` Christian Reis
2003-07-20 23:28                 ` Trond Myklebust
2003-07-20 23:45                   ` Christian Reis
2003-07-21 13:08                     ` Bogdan Costescu
2003-07-13  4:25   ` Lawrence Ong [this message]
2003-07-14  8:47     ` Trond Myklebust
2003-07-14 23:42       ` Lawrence Ong

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=20030713042557.GA12903@quasar.nro.au.com \
    --to=lawrence.ong@netregistry.com.au \
    --cc=nfs@lists.sourceforge.net \
    --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.