rpc.nfsd, rpc.mountd

["H.M. Dijkstra" <harmend@planet.nl>]

Hello everybody,

I'm an enthuisast runit user, all services I had planned to run under runit 
are running well. However I'm in need for some clarification on the behaviour 
of rpc.nfsd and all the other rpc.* which are part of the nfs-utils package. 
I observe the following: 

First I link in rpc.statd, which runs fine and stays 'parked' under runsv. 
Then
I start rpc.mountd, a run script similar to yours on your site, section
runscripts. Being completely hooked on the idea of having *all* processes
started by runit monitored by runit I see rpc.mountd remaining 'parked' under
runit, but the 8 threads of nfsd and 1 thread of lockd jumped ship and are 'on
their own' sitting in the root process tree. Ok, I might sound a nit esoteric 
so
I'll provide an example here:

--------example----------
1738 ?        S      0:00  \_ runsv nfs.mountd
2656 ?        S      0:00  |   \_ /command/svlogd -tt
/var/log/supervise/nfs.mountd
2671 ?        S      0:00  |   \_ /usr/sbin/rpc.mountd -F --no-nfs-version 2
--nfs-version 3
1739 ?        S      0:00  \_ runsv nfs.statd
2607 ?        S      0:00  |   \_ /command/svlogd -tt
/var/log/supervise/nfs.statd
2622 ?        S      0:00  |   \_ /sbin/rpc.statd -F
1740 ?        S      0:00  \_ runsv portmap
1744 ?        S      0:00  |   \_ /command/svlogd 
-tt /var/log/supervise/portmap
1826 ?        S      0:00  |   \_ /sbin/portmap -d
1742 ?        S      0:00  \_ runsv crond
1753 ?        S      0:00      \_ /command/svlogd -tt /var/log/supervise/crond
2578 ?        S      0:00      \_ crond -d1 -l10
2683 ?        S      0:00 [nfsd]
2684 ?        S      0:00 [nfsd]
2685 ?        S      0:00 [nfsd]
2686 ?        S      0:00 [nfsd]
2687 ?        S      0:00 [nfsd]
2688 ?        S      0:00 [nfsd]
2689 ?        S      0:00 [nfsd]
2690 ?        S      0:00 [nfsd]
2691 ?        S      0:00 [lockd]
--------example----------

I don't mind this per se, because I know these nfsd en lockd threads are
kernelspace processes and cannot be controlled by your runit for that 
particular
reason and even if it could I suppose this would mean a too much of burden to
control by means of context switching. This however also means the threads
cannot be killed using runit. If I want to do that I have to resort to manual
hard killing (-1, -9)

And now the questions:

1) Am I right in stating that this is the normal behaviour or is there 
something
wrong with my run script? I suppose not, but it would be very nice to have 
this
confirmed by you. Server is now production ready as far as I am concerned but
I'm not 100% sure about this yet, regarding nfs. 

2) Is it advisable to have a 'kill all nfsd/lockd threads by pid` in the 
finish
script yes?

I would be very thankful if anybody could enlighten me with these last bits 
for my perfect server.


Regards,

Harmen Dijkstra