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 (granted, the init scripts are actually named differently than the package names, but you should see my point) sean
Attachment:
signature.asc
Description: Digital signature