======================================================
> > The oddity was that with the check "/var/run/mailman/mailman.pid" -- the
> > subscribe log was getting written but not the post.
> >
> > /var/log/mailman/subscribe /var/log/mailman/post {
> > ...
> > }
>
======================================================
> The subscribe log gets written often by the web CGIs. These are
> stand-alone, short lived processes, so they will always write to
> subscribe.log. However, if a qrunner writes to the subscribe log, it
> will continue to write to the rotated subscribe.log.1 even though the
> CGIs are writing to subscribe log. Thus you may find that while
> subscribe was being written, there were also new entries in subscribe.i
> written by CommandRunner when processing email commands.
>
> Some logs including post, smtp and smtp-failure logs, are only written
> by Oby a qrunner so the new *.log won't get written until the runner is
> restarted or is SIGHUP'd either directly or by mailmanctl reopen.
======================================================
Thanks Mark, that knowledge is very useful, and much appreciated.
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
