From owner-freebsd-questions Sun Feb 28 15:50:16 1999 Delivered-To: freebsd-questions@freebsd.org Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by hub.freebsd.org (Postfix) with ESMTP id 5C67815344 for ; Sun, 28 Feb 1999 15:48:57 -0800 (PST) (envelope-from grossjoh@ramses.informatik.uni-dortmund.de) Received: from ramses.informatik.uni-dortmund.de (ramses.cs.uni-dortmund.de [129.217.20.180]) by waldorf.cs.uni-dortmund.de with SMTP id AAA17186 for ; Mon, 1 Mar 1999 00:48:40 +0100 (MET) Received: (grossjoh@localhost) by ramses.informatik.uni-dortmund.de id AAA29750; Mon, 1 Mar 1999 00:48:39 +0100 To: freebsd-questions@freebsd.org Subject: Restarting daemon started from /etc/rc*? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Kai.Grossjohann@CS.Uni-Dortmund.DE Date: 01 Mar 1999 00:41:51 +0100 Message-ID: <86btiem6yo.fsf@slowfox.frob.org> User-Agent: Gnus/5.070078 (Pterodactyl Gnus v0.78) Emacs/20.3 Lines: 23 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think one thing which is nice about SysVile is the fact that one can easily start and stop daemons which are usually run at system startup. Suppose the foo daemon has died for some reason, then I just do "cd /etc/init.d ; ./foo stop ; ./foo start" to restart it. There seems to be no similar mechanism for FreeBSD. Many daemons do useful things when sent a HUP signal, but suppose the process has disappeared for some reason? I was bitten by this when playing around with my isdnd configuration. I was almost happy when I discovered that isdnd will reread its config file when sent a SIGHUP, but then I made a little typo in isdnd.rc and the SIGHUP made isdnd disappear :-( There seems to be no simple way to start isdnd with the right parameters once it has disappeared. Have I overlooked something, or have I found an area which could be improved on in FreeBSD? kai -- I like _b_o_t_h kinds of music. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message