On 2021-05-05 19:12:24 +0200, Michael Biebl wrote: > Am 05.05.2021 um 18:39 schrieb Vincent Lefevre: > > This issue needs to be fixed anyway. If logrotate doesn't provide such > > a facility, the fix could be done in rsyslog via a locking mechanism > > to avoid the race (the /usr/lib/rsyslog/rsyslog-rotate script would > > hold the lock until it knows that the SIGHUP has been processed). > > Signals are asynchronous, I don't see how such a script could be implemented > robustly.
rsyslogd gives information when it has received a SIGHUP, e.g. May 05 18:34:05 zira rsyslogd[1700043]: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="1700043" x-info="https://www.rsyslog.com";] rsyslogd was HUPed -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
