This takes care of all basic daemonization. It uses an optional argument for STDOUT and STDERR, or /dev/null otherwise. Emancipates your process from it's shell. Behaves as a good citizen. requires POSIX. Mostly cut/paste from the manual pages.
sub daemonize { require POSIX; my $logfile = shift; $logfile = '/dev/null' unless defined $logfile; chdir '/' or die "Can't chdir to /: $!"; open STDIN, '/dev/null' or die "failed opening STDIN: $!"; open STDOUT, ">>$logfile" or die "failed opening logfile $logfile: + $!"; { defined(my $pid = fork) or die "Can't fork: $!"; exit if $pid; } POSIX::setsid() or die "Can't start a new session: $!"; open STDERR, '>&STDOUT' or die "Can't dup STDOUT for STDERR: $!"; return 1; }

In reply to Yet Another Daemonization Stub by Aighearach

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.