Re: [systemd-devel] Q: Implementing logrotate's postrotate with systemd

2019-06-11 Thread Reindl Harald
Am 11.06.19 um 13:34 schrieb Ulrich Windl: > I have a forking service (with a PID file) that can reopen the logfile after > receiving SIGHUP. In the past I had implemented "rc{service} rotate" to send > SIGHUP to the daemon as "postrotate" action. After converting (actually being > converted ;

Re: [systemd-devel] Q: Implementing logrotate's postrotate with systemd

2019-06-11 Thread Michael Biebl
A separate oneshot service sounds like overkill. I would probably use something like `systemctl kill -s HUP ${service}.service` If your sevices spawns multiple processes and you only want to send SIGHUP to the main process, you should add a `--kill-who=main` All documented nicely in https://www.fr

[systemd-devel] Q: Implementing logrotate's postrotate with systemd

2019-06-11 Thread Ulrich Windl
Hi! I have a forking service (with a PID file) that can reopen the logfile after receiving SIGHUP. In the past I had implemented "rc{service} rotate" to send SIGHUP to the daemon as "postrotate" action. After converting (actually being converted ;-)) to systemd I dropped the LSB script, and won