Test this very well first, of course. The actual time between 'date' executions will be greater than 1 second, since 'date' (and 'sleep') require some time to run themselves.
A rather extreme example from a Windows machine: Thu, Mar 22, 2012 8:24:00 AM Thu, Mar 22, 2012 8:24:01 AM Thu, Mar 22, 2012 8:24:02 AM Thu, Mar 22, 2012 8:24:03 AM Thu, Mar 22, 2012 8:24:05 AM Thu, Mar 22, 2012 8:24:06 AM Thu, Mar 22, 2012 8:24:07 AM Thu, Mar 22, 2012 8:24:08 AM Thu, Mar 22, 2012 8:24:09 AM Thu, Mar 22, 2012 8:24:11 AM (That threw me off something fierce...) -rt On Tue, Mar 20, 2012 at 18:23, Spacy <[email protected]> wrote: > Hi, > > set up a cron script to execute on June, 30th 23:59:00 UTC: > > for i in `seq 0 120`; do date; sleep 1; done > > > This will print the current date for 120 seconds. Standard out is usually > mailed to root or the script owner. Refer to your cron documentation for the > details. > More of a hack, than a solution, but should work ;-) -- Ryan Tucker <[email protected]> _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
