On Monday March 19, [email protected] wrote:
>
>
> Olaf Kirch wrote:
> > On Monday 19 March 2007 02:14, Neil Brown wrote:
> >> 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).
> >
> > Can't speak for others, but this is the reason why Suse put it into /sbin too,
> > as long as they shipped it.
> I can only assuming this was the case as well... Red Hat has
> been putting both rpc.lockd and rpc.statd in /sbin
> since at least RH 7.1
>
Ok.... so the only reason for moving to /sbin is a reason that I don't
think is a good one. I think I won't move it in 'upstream'.
So people should really mount '/usr' (and '/var') with 'nolock' (which
should really be spelt 'locallocks' or similar). But they probably
don't.
So how about this: In a similar way that we now try to start statd if
'nolock' is not set, we could set 'nolock' if we fail to start statd
(and it isn't already running). What do people think of that?
I should probably add an rpc ping to check if statd is running rather
than just looking in /var/run/rpc.statd.pid, but the principle seems
sound....
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
At 01:12 AM 3/22/2007, Neil Brown wrote:
>So how about this: In a similar way that we now try to start statd if
>'nolock' is not set, we could set 'nolock' if we fail to start statd
>(and it isn't already running). What do people think of that?
Gack. At worst, the mount should fail, instead of silently changing the
mount to one which may break application semantics! This would change
the default behavior in a way the admin couldn't override. Besides,
what's to say statd won't die later?
Tom.
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs