From owner-freebsd-current Sun May 7 14:47:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 5C6B937C0BD; Sun, 7 May 2000 14:47:12 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA60253; Sun, 7 May 2000 14:47:05 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <3915E459.2C1A382C@gorean.org> Date: Sun, 07 May 2000 14:47:05 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0422 i386) X-Accept-Language: en MIME-Version: 1.0 To: Will Andrews Cc: FreeBSD Ports , FreeBSD Current Subject: Re: rc.d startup scripts References: <20000506155749.K55274@argon.blackdawn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will Andrews wrote: > > Hello, > > I've noticed an inconsistency among our ports. It seems that not every port > that installs rc.d startup scripts includes methods to not only startup, > but also shutdown and/or restart, where appropriate. (Sent to -ports for > ports hackers' opinions.) Dave already mentioned the right targets, and I agree that it would be nice to have this. I have some sample stuff that I've used for quite a while that I'd be happy to clean up and share as templates. One thing we can do which will improve the situation right off the bat is standardize the code that does the pid-finding, etc. and then source those functions in each control script. > Shouldn't this sort of thing be standardized? And maybe a similar method be > integrated into /etc/rc for restarting base system daemons? (Sent to > -current for src hackers' opinions.) I'm going to reply to the system part of this too, replies to this thread should split off to -current. I have a design in mind for a new rc system that uses scripts with "start, stop, status" operators to both upgrade and downgrade services, where "services" are defined as groups of daemons/programs that work together. For example, "nfs" would be an example of a service, which would be subdivided into client and server, etc. Unfortunately, due to the way work is going right now I haven't been left with any time for big projects of this nature. My plan was to start small with the daemons that don't have a lot of dependencies, then grow the system up through the top. If anyone wants more details about my ideas on this line, just let me know. Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message