Do you really need PID files?
Unix (including Linux) can do fine without PID files and their problems, and without any special deamonizing code in your program. This way also gets rid of fragile init scripts and silly tools like start-stop-daemon that don't even attempt to handle a crashing service. Plus, you get reliable logging including rotating logs for free.
See Re: How to get the process Id, Re: current best practices for Perl-daemons on Linux, Re: A few questions regarding Proc::Daemon, Re: Log File Rotation, Re: RFC: an(other) UNIX daemon module implementation, Re: Problems with forking, Re^3: Proc::PID::File problem generating pid files, or: does it matter where a pid file lives?, daemontools, the djb way, SuperSearch.
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
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.