Here are some suggestions, all of which have shortcommings.
You'll need to decide if there are special cases that will
keep these from working, so YMMV.
You could backup and remove all files at system startup if
you know you'll get to them before the application starts
up.
You could delete all zero sized files that were older
than the last boot time of the machine (or just some really
old date if you can't get the boot time and can live
with an occasional missing log file).
If the files
have a PID in the name, common on Unix systems, you could
parse out the PID, and then see if the process
still exists with the same PID, and if not remove the file.
bluto
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.