On Wed, May 11, 2011 at 01:50:30PM +0200, Michael Biebl wrote: Hi,
> > When running as a systemd service rsyslog does not support the reload > > action. > > Consequently, actions like logrotate that want to reload the service fail. > > > > mail.svr01.mucip.net:~# invoke-rc.d rsyslog reload > > Reloading rsyslog configuration (via systemctl): rsyslog.serviceFailed to > > issue method call: Job type reload is not applicable for . > > failed! > > invoke-rc.d: initscript rsyslog, action "reload" failed. > > > > Please supply a ExecReload line in the systemd unit file. I use this locally > > and it works just fine > > > > ExecReload=/bin/kill -HUP $MAINPID > > > > See: > http://git.adiscon.com/?p=rsyslog.git;a=commit;h=da75472096c45dd136d41c6e9ad7bf740069d3a1 > > > which was later reverted: > http://git.adiscon.com/?p=rsyslog.git;a=commit;h=fd26a42bdc04eaf497cafd9ef806a54f3de1a7e9 | systemd: do not hook up SIGHUP for reload | | rsyslog doesn't actually do a configuration reload on SIGHUP, hence | let's not pretend it does and drop the ExecReload= line, so that the | clients will rather restart than reload the service. Hrm, what to do then? This currently breaks logrotate, because logfiles aren't reopened after being renamed. Assign to logrotate? But running invoke-rc.d reload is probably the most portable way to do it. Bernhard -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
