Hi all, I've been using Schedule::Cron, and it's been working well. My one gripe is that there's no reference to the script (vdcs_errors.pl) that calls the cron job in the process table. In other words, if I grep the process table for the PID of the perl script (i.e. the contents of the variable $$), I get the following, which has no mention of vdcs_errors.pl:
# ps auwwx | grep 3166 root 31663 0.1 0.0 66376 5600 pts/5 S 02:53 0:00 Schedul +e::Cron MainLoop - next: Mon Jun 19 15:00:00 2006
I tried using nofork => 1 when defining the cron object, but still the same thing. I also looked at Schedule::Cron::Nofork, and I'm a little leery of what it says, since I may be using this for other jobs: Anybody have ideas? Perhaps it's not hitting me from reading the documentation on cpan.

-- Burvil


In reply to Schedule::Cron process name? by bowei_99

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.