I wonder why nobody has mentioned it yet, but there is Schedule::Cron, and a nonforking subclass, Schedule::Cron::Nofork (this one is written by me but planned to be included within Schedule::Cron in the next release as far as I gather).

These modules allow you easy scheduling via a permanently running script, and then either forking or running a command, waiting for it to end.

Some code I have running on my PC (under NT) :

#!/usr/bin/perl -w use strict; use Schedule::Cron::Nofork; use File::Spec; use FindBin; use Logger qw(my.email@my-work.net); my $cron = Schedule::Cron::Nofork->new( sub { my $self = shift; warn "$$ Running $_[0]\n"; system("start \"Cron: $_[0]\" \"$_[0]\""); }); warn "Starting cron\n"; $cron->add_entry("0,5,10,15,20,25,30,35,40,45,50,55 18 * * 1-5", RUN = +> File::Spec->catfile( $FindBin::Bin, "transfer-OPICS-Vertex-53.pl" ) +); $cron->add_entry("0,5,10,15,20,25,30,35,40,45,50,55 18 * * 1-5", RUN = +> File::Spec->catfile( $FindBin::Bin, "transfer-OPICS-SapBCA-53.pl" ) +); $cron->add_entry("0,5,10,15,20,25,30,35,40,45,50,55 18 * * 1-5", RUN = +> File::Spec->catfile( $FindBin::Bin, "transfer-OPICS-SapFi-53.pl" )) +; #$cron->add_entry("* * * * 1-5", RUN => File::Spec->catfile( $FindBin: +:Bin,"test.pl")); $cron->run();

I start the scripts via start, because I don't need and don't trust the built-in forking simulation - it's amazing that it works, but for a simple script that dosen't really need the resource sharing features, I avoid it.

perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ; # The $d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider ($c = $d->accept())->get_request(); $c->send_response( new #in the HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' # web

In reply to Re: Scheduling with Perl? by Corion
in thread Scheduling with Perl? by EyeOpener

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.