I strongly disagree that this is how file locking
should work. It is how it
does work on
Windows, but it is not how it works on Unix. The result
is that you have an additional piece of complexity on
Unix that applications need to be aware of, but when you
are dealing with shared resources, the Windows behaviour
is (in my experience) far harder to administer.
Furthermore it can be very convenient. For instance as
a debugging aid it can be very nice to type in:
tail -f /var/log/apache/error.log
and watch the result of writes made by Apache to its error
log in real time as you are interacting with the browser.
(Writes which you get in there with well-placed
warn
statements...) This
works just fine on Unix. But Windows makes it far too
easily for an application to make this kind of interaction
impossible. :-(
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.