No offense but this doesn't really sound like a problem with the module. The truth is you should be managing your disk space properly. Look into Nagios it will monitor disk space (among many other things) for you.

Looking at current source, I see a die when file can not be written, so I assume you are evaling the Proc::PID::File->running() call and disregarding the result. But I can't tell for certain because you didn't post any code. It does die for me when I try to assign it to my CD.

IIRC, you can also clear your program's pid files at the beginning of reboot in rc.sysinit

UPDATE:
Since our data changes a lot, the slave quickly filled up the disk. I don't think monitoring tools would have avoided me waking up to a thrashing box.

Sure it could - I've written many Nagios Plugins. All of them before helpful modules like Nagios::Plugin. Writing Nagios plugin are not difficult, that's why I like it. You could easily monitor the number of file to be processed. Not to mention that Nagios also has CPU and Memory (and IIRC swapping monitors) already built in.

grep
1)Gain XP 2)??? 3)Profit

In reply to Re: Whoa! looking for a better pidfile module by grep
in thread Whoa! looking for a better pidfile module by rhesa

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.