From owner-freebsd-current Sun May 7 1:48:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id F3D3837B87C; Sun, 7 May 2000 01:48:28 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id EAA11285; Sun, 7 May 2000 04:34:37 -0400 Date: Sun, 7 May 2000 04:34:37 -0400 (EDT) From: Mike Nowlin To: Will Andrews Cc: "Brandon D. Valentine" , FreeBSD Ports , FreeBSD Current Subject: Re: rc.d startup scripts In-Reply-To: <20000506191401.A56777@argon.blackdawn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Fine, you can quote historical context to argue against doing something > similar to SVR4 init. I, however, see nothing wrong with making it easier > to manage the daemons. Of course, that does not necessarily need to go in > the rc.d scripts. This is as it should be.. "rc" files (and directories) are (in my opinion) meant to hold required configuration and startup information, NOT stuff that sends SIGHUP to Apache. Gated got it right - add a simple program (gdc) that does the extra stuff. If we could get the ports maintainers to supply a script that does the extra stuff and install it as part of the port, that could be a mild inducement on the behalf of FreeBSD. I dunno how many times I've typed "ps ax|grep dumbproc ... kill somepid .... dumbproc" or something like that. "restart dumbproc" would be easier, and unique enough that there wouldn't be any major naming collisions. Create system-wide "restart", "start", and "stop" scripts that the ports maintainers could plug into for those functions... Mebbe not a bad idea for half of the base system programs as well -- wouldn't change the BSD way of doing things, but would add some extra ease-of-use... Just make SURE that people don't start calling "restart lpd" from script files, as that could break things when it comes to porting to other BSD variants. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message