Date: Wed, 19 May 1999 13:31:12 +0200 From: Marcel Moolenaar <marcel@scc.nl> To: Achim Patzner <ap@bnc.net> Cc: Hellmuth Michaelis <hm@hcs.de>, isdn@FreeBSD.ORG Subject: Re: Rename on SIGUSR1 for isdnd Message-ID: <3742A100.42141BEA@scc.nl> References: <3741EFAE.5C0BFD63@scc.nl> <m10k0sp-0000fgC@hcswork.hcs.de> <19990519124325.G51180@bnc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Achim Patzner wrote: > > The idea behind isdnd's current behaviour is to have a shell script which > > renames isdnd's log file and then send a SIGUSR1 signal to isdnd. > > Which is the way it has been done for ages[tm]. > > > Comments ? > > Yes. Renaming is violating the principle of causing the least surprises. I'm more sensitive to your first remark. Maybe I'm not easily surprised anymore :-) To add something to the argument, I have a newsyslog.conf file with 18 lines and none of them has a pidfile/signal specification. IIRC, the possibility to specify them, so newsyslog could send a signal to the process (which btw defaults to SIGHUP and not SIGUSR1) is recent WRT to your remark that it is done for ages. So, not surprisingly, both your statements are not as absolute as you put them. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3742A100.42141BEA>