>>>>> "RN" == Ranga Nathan <[EMAIL PROTECTED]> writes:
RN> I have found a number of modules for programmatic scheduling of cron. It
RN> would help me to hear from the public about their experiences (if they
RN> have used it). Stem would be good but it may be more than I can chew for
RN> my simple requirements. Uri may convince me otherwise.
how so? just using stem with the cron module is 2 minutes of work. here
is a simple config file for it:
# cron.stem
#
[
class => 'Stem::Console',
],
[
class => 'Stem::Demo::Cmd',
name => 'cmd',
],
[
class => 'Stem::Cron',
name => 'cron',
args => [
'hours' => [ 0 .. 8 ],
'month_days' => [ '11-15' ],
'months' => [ '12' ],
'msg' => [
'to_cell' => 'console',
'data' => "foo\n",
]
],
],
the console cell is optional but useful for debuging and status
stuff. the Stem::Demo::Cmd cell can be replaced by your cell or your
command could be run from it. the stem::cron cell has the same args (but
spelled out and all are optional) as cron itself. when this gets
triggered it sends out the message in the 'msg' field.
you run this with
run_stem cron
it can't get much simpler than that.
and it can get much more complex with little additional work. the same
message could be sent to N other locations by simply adding a
stem::switch cell and giving it the addresses where you want the message
sent. try that with regular cron when it is executing a single
command. you have to write a script to handle the remote commands and
then add that to your crontab. adding more features to cron scripts is
even more annoying.
so tell me now that normal cron is easier and simpler? :)
uri
--
Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
