From: Neil Brown <neilb@suse.de>
Subject: rpc.statd  in /sbin or /usr/sbin ??
Date: Mon, 19 Mar 2007 12:14:13 +1100
Message-ID: <17917.58341.502839.29524@notabene.brown>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: nfs@lists.sourceforge.net
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net


Hi,
 I have noticed that some distros like to install statd in /sbin
 rather than /usr/sbin.
 I would like to know why.

 If it is generally agreed that it needs to be in /sbin, then I'll
 change nfs-utils to install it there, but as yet I am unconvinced.

 The only reason I can see for putting statd in /sbin is if it were
 needed for mounting /usr (in cases where /usr is accessed via NFS).

 However in that case (as in the case for an NFS root), I think it is
 appropriate to use the "nolock" flag on the basis that /usr is not
 expected to be share-writeable (i.e. either readonly or
 single-client).  In that case there is no need for locking requests
 to go over the network, and no need for statd to be running before
 /usr is mounted.

 So: can anyone try to convince me that rpc.statd should go in /sbin??

Thanks,
NeilBrown

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