In fact it is not guaranteed. We reinvented our log wheel and 95% of log activity is on the same log file, and we find it very useful.
From perl docs, various web examples, this merlyn's webcolumn (written when I didn't even know what perl was) and extensive™ testing, I learnt that using flock() with LOCK_EX flag is the only way to have consistent updates/writes by many processes onto a single log file (or page-counters, for that matter), though this method is not reliable across platforms.
Not using flock resulted in mangled log files, with different processes log buffers being mixed and truncated at random.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.