> Hi NFS folks, I am still fighting witn nfsd/lockd not dying
> upon killall5. (they are stuck in D state for 2 mins and then
> die with "rpciod: active tasks at shutdown?!" at console)
> I found out that nfsd and lockd die as expected when I use
> modified killall5 which do not SIGSTOP all tasks before killing
> them.
> Any idea why this makes such difference? Is this a bug in
> nfsd/lockd or in killall5?
killall5 is a bad idea as a method for killing nfsd/lockd. You are
better off using something more targeted so you can ensure the correct
ordering.
If you kill the portmapper before the nfs/lockd daemons have finished
unregistering their services then the above behaviour is completely
normal.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/