[Bug 265868] Re: mailmanctl reopen does not reopen all log files
Mark Sapiro
mark at msapiro.net
Tue Sep 25 07:17:21 CEST 2012
What should we look into? All I see from your comment is that process
number 14402 had units 3 and 5 connected to /var/log/mailman/error and
unit 6 connected to /var/log/mailman/qrunner. You then removed and
recreated var/log/mailman/error and 'reopened' Mailman's logs, and you
see that the process's units 3 and 5 were associated with the deleted
var/log/mailman/error file.
This is how it works. Should something actually be logged to Mailman's
error log, at that time, the deleted file will be detached and the unit
opened to the new file. Do you have any evidence that this doesn't work?
The reopen function is intended to be used with something like logrotate
to switch to the new log when it is first written following a rotate. A
typical logrotate script is
/var/log/mailman/bounce /var/log/mailman/error (and the rest) {
missingok
sharedscripts
postrotate
/usr/local/mailman/bin/mailmanctl reopen >/dev/null 2>&1 || true
endscript
}
This works. If you have any evidence to the contrary, please post
details.
** Changed in: mailman
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/265868
Title:
mailmanctl reopen does not reopen all log files
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/265868/+subscriptions
More information about the Mailman-coders
mailing list