Daemonizing isn't hard but the source code for Proc::Daemon sure makes it look hard. My searching for daemonize didn't find anything simpler. Maybe there is a bug hidden in that complexity. Just keep it simple?

use POSIX 'setsid'; $SIG{HUP} = 'IGNORE'; #chdir('/') # Not required in your case; maybe not desired. # or die "Can't cd /: $!\n"; for( 1,0 ) { my $pid = fork(); die "Can't fork: $!\n" if ! defined $pid; exit if $pid; if( $_ && -1 == setsid() ) { die "Can't setsid: $!\n"; } } open STDIN, '<', '/dev/null' or die "STDIN: $!\n"; open STDOUT, '>', '/dev/null' or die "STDOUT: $!\n"; open STDERR, '>&', \*STDOUT or die "STDERR: $!\n";

At least that will split the difference as to if the problem is a bug in daemonization when you use that module in that way.

- tye        


In reply to Re: Proc::Daemon not detaching (KISS) by tye
in thread Proc::Daemon not detaching by Dave Howorth

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.