On Fri, Mar 31, 2006 at 06:28:14AM -0500, sean finney wrote: > On Fri, Mar 31, 2006 at 09:47:59AM +0200, Wouter Verhelst wrote: > > What I'm suggesting is, actually, the reverse of a pidfile, in some way. > > You'd still have your /var/run/syslogd.pid; but, assuming that file > > contained the PID "2722" (as it currently does on my system), you'd also > > have a file called "2722" somewhere (say, under "/var/run/pidlookups") > > which would contain "/etc/init.d/sysklogd". > > > > With such a system, you'd be able to say "restart whatever PID 2722 is". > > Or even to force-reload it, if that'd be enough. > > no offense, but this sounds more like a solution looking for a problem > than the other way around. > > i also don't see how it is aesthetically better or cleaner than > the following 4 lines of shell code: > > sysloginits="inetutils-syslogd metalog socklog-run sysklogd syslog-ng" > for s in $sysloginits; do > test -x /etc/init.d/$s && invoke-rc.d $s restart || true > done
* This doesn't scale as well. Maybe not so important if all you ever care about is syslog and udev, but there might be more cases where such a thing could be interesting and/or important. * It requires a manual update of the package every time someone adds a new syslogd to the archive. Mine does not. * It would also catch daemons that have /dev/log open, while "just" restarting syslogd won't cut that. -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
