Le 16 août 2018 14:07:41 GMT+02:00, Abhijith PA <[email protected]> a écrit : > > >On Thursday 16 August 2018 05:19 PM, Pierre-Elliott Bécue wrote: >> Control: severity -1 normal >> Control: tags -1 + moreinfo > >> Hi Abhijith, >> >> Thanks for your report. >> >> First, a SIGHUP is not a restart. Do you have any intel that suggests >your >> instance is actually restarted? >> >> Also, have a look at `/etc/logrotate.d/mailman3` >> >> ``` >> /var/log/mailman3/mailman.log { >> daily >> rotate 5 >> compress >> delaycompress >> missingok >> notifempty >> create 640 list list >> postrotate >> if /etc/init.d/mailman3 status >/dev/null; then \ >> /usr/bin/mailman reopen >/dev/null; \ >> fi; >> endscript >> } >> ``` >> >> The postrotate part calls "reopen" if mailman3 is running. reopen is >a >> control command that sends sighup to the master process, hence the >log line. >> >> See `/usr/lib/python3/dist-packages/mailman/commands/cli_control.py` >for more >> intel. >> >> Can you provide me with more information? So far it seems that your >bug >> isn't one. >> >> Best regards, >> > >Hi Pierre. >Thanks for your reply. Seems like that is the cause. I don't have any >other intel. > >I will close this bug. > >--abhijith
Hi, You are welcome. If you think this behaviour should be changed or if you see any issue I'm happy to work on it. By the way what does a ps aux | grep mailman give you regarding the start time of mailman3 ? Cheers, -- PEB
