From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Haakon Riiser <haakon.riiser@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: lockd: rejected NSM callback from 7f000001:30001
Date: Fri, 01 Sep 2006 12:11:11 -0400 [thread overview]
Message-ID: <1157127071.5632.59.camel@localhost> (raw)
In-Reply-To: <20060901132854.GA25597@bigboss.venod.com>
On Fri, 2006-09-01 at 15:28 +0200, Haakon Riiser wrote:
> A few months ago, I upgraded my file server from FC3 to FC5,
> and at the same time, upgraded all of the file server's hardware
> except the disks (a single SATA drive that holds the OS plus four
> SATA drives in a software RAID5 array).
>
> After this upgrade (at least that's when I think it first started to
> happen), I started seeing
>
> lockd: rejected NSM callback from 7f000001:30001
This is very intentional. The kernel won't accept notifications from
unprivileged ports. If it did, then any local user would be able to
trick the kernel into thinking that some server had rebooted, by sending
the appropriate RPC message.
Change your /etc/sysconfig/nfs so that it sets a value < 1024 for
STATD_OUTGOING_PORT.
Cheers,
Trond
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-09-01 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 13:28 lockd: rejected NSM callback from 7f000001:30001 Haakon Riiser
2006-09-01 16:11 ` Trond Myklebust [this message]
2006-09-01 16:54 ` Haakon Riiser
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=1157127071.5632.59.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=haakon.riiser@fys.uio.no \
--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