From: Steve Dickson <SteveD@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: HEADS-UP: nearing nfs-utils 1.1.0 and statd changes.
Date: Tue, 20 Mar 2007 08:32:37 -0400 [thread overview]
Message-ID: <45FFD465.4@RedHat.com> (raw)
In-Reply-To: <17914.20117.186786.830574@notabene.brown>
Neil Brown wrote:
> I have changed the default so that statd now compiled with
> RESTRICTED_STATD, so that it only listens to locked for monitor
> requests. Everyone else is ignored. There is no-one else who uses
> statd anywhere, so this should be perfectly safe and is more secure.
It just occurred to me that this may not be a good idea... Unless
there has been some changes in the area, turn this on will
break locking... The reason I know this is that I turned it on
at one point and people started to see the following messages
being logged:
nsm_mon_unmon: rpc failed, status=-13
lockd: cannot monitor 192.168.1.202
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140385
has the details...
steved.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-20 12:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 8:00 HEADS-UP: nearing nfs-utils 1.1.0 and statd changes Neil Brown
2007-03-16 12:59 ` Talpey, Thomas
2007-03-18 23:02 ` Neil Brown
2007-03-19 18:40 ` Talpey, Thomas
2007-03-22 4:54 ` Neil Brown
2007-03-22 12:36 ` Talpey, Thomas
2007-03-16 14:03 ` Steve Dickson
2007-03-16 14:30 ` Kevin Coffman
2007-03-18 22:52 ` Neil Brown
2007-03-16 18:10 ` J. Bruce Fields
2007-03-18 23:49 ` Neil Brown
2007-03-19 23:02 ` J. Bruce Fields
2007-03-20 0:30 ` Talpey, Thomas
2007-03-20 1:14 ` J. Bruce Fields
2007-03-20 10:47 ` Talpey, Thomas
2007-03-20 11:24 ` William A. (Andy) Adamson
2007-03-20 14:26 ` J. Bruce Fields
2007-03-20 14:49 ` Talpey, Thomas
2007-03-20 14:57 ` J. Bruce Fields
2007-03-20 15:03 ` Talpey, Thomas
2007-03-20 12:32 ` Steve Dickson [this message]
2007-03-22 4:30 ` 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=45FFD465.4@RedHat.com \
--to=steved@redhat.com \
--cc=neilb@suse.de \
--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.