From owner-cvs-all Sat May 12 6:15:33 2001 Delivered-To: cvs-all@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id B7CBC37B424 for ; Sat, 12 May 2001 06:15:28 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 21002 invoked by uid 0); 12 May 2001 13:15:27 -0000 Received: from p3ee21676.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.118) by mail.gmx.net (mp007-rz3) with SMTP; 12 May 2001 13:15:27 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id KAA24811 for cvs-all@freebsd.org; Sat, 12 May 2001 10:18:47 +0200 Date: Sat, 12 May 2001 10:18:47 +0200 From: Gerhard Sittig To: cvs-all@freebsd.org Subject: Re: $EDITOR $CONF && kill -HUP $PID (was: cvs commit: doc/en_US.ISO_8859-1/books/handbook/advanced-networking chapter.sgml) Message-ID: <20010512101846.G253@speedy.gsinet> References: <20010511195046.B1672@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from rwatson@freebsd.org on Fri, May 11, 2001 at 04:59:55PM -0400 Organization: System Defenestrators Inc. Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ the subject looks this funny to avoid religious wars on editors and stuff :) ] On Fri, May 11, 2001 at 16:59 -0400, Robert Watson wrote: > > On Fri, 11 May 2001, Wilko Bulte wrote: > > > > Would this be something for FreeBSD? I, for one, tend to > > forget this kill -1 thingy. > > Maybe it's just me, but I hate it when I discover "automagic" > things like that. As the administrator, I know when the > contents of the file /etc/exports will be consistent on disk, > and I indicate that to the daemon by sending it a signal. Would something like a "vicrontab(1)" - or whatever it could be named - wrapper be appropriate? This idea does a great job on regenerating password databases from their text representation already. Another hack(?) could be some Makefile style thing, much like there is in /etc/mail or next to your DNS database. But I wouldn't know which criterion describes best the fact that a running daemon hasn't seen a new config file yet ("[ $CONF -nt $PID ] && kill -HUP `cat $PID`"? but this would require the daemon to touch or rewrite the pidfile upon reload -- or the Makefile had to keep track). > I'm all for making restarting daemons easier -- you can imagine > a daemonctl or something that speaks "restart" for a bunch of > daemons, but automagic can sometimes hurt you more than it > helps you. Starting / stopping / hupping / 'stat'ing / etc daemons would be easier if /etc/rc granularity was finer and the pieces would look like the /usr/local/etc/rc.d scripts. But past discussions usually turned into "that's a Linux thing and therefor cannot be good for us". :> I understand that splitting logically oriented groups is not the problem but the wrapper to keep the sequence (would be nice: while obeying dependencies) is. And there have been concerns that repeated "source"ing of config files slows operation down (although I estimate that we talk about single seconds - if at all - once in a boot sequence; plus code has been sketched to flag an already read file by a variable). virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message