From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/718 Path: main.gmane.org!not-for-mail From: "H.M. Dijkstra" Newsgroups: gmane.comp.sysutils.supervision.general Subject: rpc.nfsd, rpc.mountd Date: Sat, 19 Feb 2005 15:02:39 +0100 Message-ID: <200502191502.39778.harmend@planet.nl> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1108822325 8078 80.91.229.2 (19 Feb 2005 14:12:05 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 19 Feb 2005 14:12:05 +0000 (UTC) Original-X-From: supervision-return-957-gcsg-supervision=m.gmane.org@list.skarnet.org Sat Feb 19 15:12:04 2005 Original-Received: from antah.skarnet.org ([212.85.147.14] ident=qmailr) by ciao.gmane.org with smtp (Exim 4.43) id 1D2VKx-0001L4-1t for gcsg-supervision@gmane.org; Sat, 19 Feb 2005 15:11:59 +0100 Original-Received: (qmail 25299 invoked by uid 76); 19 Feb 2005 14:15:25 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 25293 invoked from network); 19 Feb 2005 14:15:25 -0000 Original-To: supervision@list.skarnet.org User-Agent: KMail/1.7.2 Content-Disposition: inline X-Virus-Scanned: ClamAV 0.80/705/Fri Feb 11 17:51:32 2005 clamav-milter version 0.80j on mailrelay02 X-Virus-Status: Clean X-MailScanner-To: gcsg-supervision@gmane.org Xref: main.gmane.org gmane.comp.sysutils.supervision.general:718 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:718 Hello everybody, I'm an enthuisast runit user, all services I had planned to run under runit= =20 are running well. However I'm in need for some clarification on the behavio= ur=20 of rpc.nfsd and all the other rpc.* which are part of the nfs-utils package= =2E=20 I observe the following:=20 =46irst I link in rpc.statd, which runs fine and stays 'parked' under runsv= =2E=20 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' und= er 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 esoter= ic=20 so I'll provide an example here: =2D-------example---------- 1738 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0\_ runsv nfs.mountd 2656 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0| =A0 \_ /command/svlogd -tt /var/log/supervise/nfs.mountd 2671 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0| =A0 \_ /usr/sbin/rpc.mountd -F= --no-nfs-version 2 =2D-nfs-version 3 1739 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0\_ runsv nfs.statd 2607 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0| =A0 \_ /command/svlogd -tt /var/log/supervise/nfs.statd 2622 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0| =A0 \_ /sbin/rpc.statd -F 1740 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0\_ runsv portmap 1744 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0| =A0 \_ /command/svlogd=20 =2Dtt /var/log/supervise/portmap 1826 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0| =A0 \_ /sbin/portmap -d 1742 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0\_ runsv crond 1753 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0 =A0 =A0\_ /command/svlogd -tt /= var/log/supervise/crond 2578 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 =A0 =A0 =A0\_ crond -d1 -l10 2683 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2684 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2685 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2686 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2687 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2688 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2689 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2690 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [nfsd] 2691 ? =A0 =A0 =A0 =A0S =A0 =A0 =A00:00 [lockd] =2D-------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=20 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 manu= al hard killing (-1, -9) And now the questions: 1) Am I right in stating that this is the normal behaviour or is there=20 something wrong with my run script? I suppose not, but it would be very nice to have= =20 this confirmed by you. Server is now production ready as far as I am concerned b= ut I'm not 100% sure about this yet, regarding nfs.=20 2) Is it advisable to have a 'kill all nfsd/lockd threads by pid` in the=20 finish script yes? I would be very thankful if anybody could enlighten me with these last bits= =20 for my perfect server. Regards, Harmen Dijkstra