The solution that I use is to use the unix "at" command
to launch the process. This is very simple to do, and if
your cron is configured properly any messages printed by
the job will be sent to you in an email (assisting
greatly in debugging). A draw-back, though, is that this
is inappropriate for long-running processes. For those I
tend to use a cron that tries to restart the process, and
then check at startup to see if it is running. (Usually
by trying to grab a file lock.)
For a poor man's parallel process control you can modify
this by specifying a random queue to send the job to. OK,
pretty poor, but it is surprising how far this one goes.
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.