There are a whole bunch of cron daemons that understand the idea of a
machine not being on 24 hours a day (anachron, hc-cron (based on vixie),
ucrond...). Their compiled executables are less than 50k on the arm.
Basically on shutdown they write a timestamp to disk and on startup
compute the difference in time and run all the jobs that should have run
in the interim. This strikes me as a decent facility to have in the ipaq
(that, and at).
But writing a 4 byte shutdown time to a 256KB flash strikes me as rather
wasteful.
Is there a tiny area of flash/non-volatile ram that already retains the
shutdown time? (assuming that ipaqs actually shut down now), or some
small space that could be used for a variety of such minor purposes
(pids, for example)
Anyone have an opinion on the quality/security of the various cron
daemons available? ucrond looks to be the most flexible, supports a
socket for monitoring events, but has some dumb limits (200 entries),
hc-cron is based on an older vixie cron....
-- ------------------------------------------------------------------------- A pile of local optimizations may easily lead to global pessimization. - Victor YodaikenReceived on Fri Sep 22 14:08:09 2000
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:43:42 EDT