First I thought I had some bad configuration, or maybe permissions
problem because I'm using package users. But several builds
later, the
issue persist. Got a feeling either not much people use NFS
anymore, or
noone really care too much about it..
--Tor Olav
Don't feel
Richard A Downing wrote:
David Fix wrote:
You know, I know this is late for a comment... But I just thought of
something... Could it be as simple as doing something like this:
kill `pgrep nfsd`
That's just an inelegant equivalent of:
rpc.nfsd -- 0
I think Tor Olav is trying to confirm
David Fix wrote:
You know, I know this is late for a comment... But I just thought of
something... Could it be as simple as doing something like this:
kill `pgrep nfsd`
That's just an inelegant equivalent of:
rpc.nfsd -- 0
I think Tor Olav is trying to confirm that the kernel threads
if pidof nfsd 21 /dev/null ; then {
rpc.nfsd -- 0
sleep 1
if pidof nfsd 21 /dev/null ; then {
echo_failure
boot_mesg Killing NFS nfsd...
Tor Olav Stava wrote:
I'm trying to wrap it in some if() statements to see if I can get a
nice solution to this, but if someone have already fixed it I would
appreciate if you share it, and maybe update the script in SVN.
After a while of trial and error, I've come up with a solution that
Richard A Downing wrote:
I think that your solution, while not seemingly elegant, is a good
workaround. rpc.nfsd is just a userland program to tell the kernel
module how many threads to run. As such, it reports success if it told
the kernel OK - what the kernel does with this info is a
