Udi Mottelo:
Ruud H.G. van Tol:
Udi Mottelo:
- If procmail will not mix the records in the logfile
I would be satisfied.
There are ways to solve that, like with TRAP.
Yes, there are ways to solve that, but doesn't application's
job? To write its logs correctly?
If procmail would not write out its log-entries until the very end, than
you would need a different log-method to write out to the log directly,
at least for debugging purposes.
Many procmails can run at the same time, and if you let them all log to
the same file and don't use locks, than the LOGs will intertwine. So it
is natural.
Maybe a switch is an idea, to choose between direct and postponed
logging, with postponed logging (that implies locking) as the default.
And an optional LOG-line-prefix, with <PID><tab> as the default. That
needs a notion if the log is at the start of a line, which it is at the
very start and after any (real) change in LOGFILE and each time after a
previous LOG-entry ended in a newline.
<big irrelevant tail snipped>
--
Grtz, Ruud
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail