On Wed 23 Jan 2013, Michael Biebl wrote: > > > > invoke-rc.d rsyslog rotate > /dev/null 2>&1 > > > > Not very nice, but at least it will silence invoke-rc.d. > > Eww, hiding real errors. I don't want to do that. > > > Alternatively the sysv-rc people might want to provide some hook for > > invoke-rc.d so that policy-rc.d might indicate what to do with unknown > > actions. I've been looking but can't find any way of suppressing the > > invoke-rc.d output via the policy layer. > > > > invoke-rc.d rsyslog rotate 2>&1 > /dev/null | grep -v 'action rotate is > > unknown' >&2 > > That is super-ugly too. > I'm > more inclined to ditch the usage of invoke-rc.d altogether and simply > call the sysv init script directly or even drop the "action" from the > sysv init script and run "kill -SIGHUP $(cat /var/run/rsyslogd.pid)" > directly in the logrotate script.
I'd do the kill -SIGHUP, after perhaps some sanity checking of the pidfile (does it exist). Thanks, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
