All of
 help / color / mirror / Atom feed
From: Lawrence Ong <>
To: Trond Myklebust <>
Subject: Re: SM_UNMON again -> kernel
Date: Tue, 15 Jul 2003 09:42:26 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Jul 14, 2003 at 10:47:52AM +0200, Trond Myklebust wrote:
> >>>>> " " == Lawrence Ong <> writes:
>      > Anyhow, it shows that the kernel is still continually sending
>      > out unmonitor packets to statd at regular intervals.  What the?
>      > Why is this happening?
> What's wrong with that: I presume you *are* releasing locks every now
> and then?

How often should you be releasing locks?  Right now, on the client and
server, it is happening about every 5 minutes.

> There's no point in monitoring a server on which you're not holding
> any locks.

Well, in that case, the only way to make the erroneous SM_UNMON really go
away is by adding: localhost mymachine to /etc/hosts.
I know you said that's bad, but how else would you do it when the MON
function for nfs-utils actually set the my_name variable to

Maybe i'm missing something, but so far, the only ways i see that the
erroneous message would ever disappear are:

a. By putting in localhost mymachine in /etc/hosts
b. By having the kernel STOP sending out unmonitor packets to statd at
   regular intervals
c. By changing statd so that it does not set my_name to
   (breaks fix? for CERT CA-99.05).

If you think that there is another way to stop that erroneous SM_UNMON
error, without doing any of those ridiculous fix above, I would be willing
to test it out.  Thanks.


This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
NFS maillist  -

      reply	other threads:[~2003-07-14 23:43 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
2003-07-14  8:47     ` Trond Myklebust
2003-07-14 23:42       ` Lawrence Ong [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.