From: Green, Simon (Simon.Green@EU.ALTRIA.COM)
Date: Fri Oct 24 2003 - 06:07:07 EDT
Killing cron is the normal way of doing this. There is no other way.
It's necessary because the cron process will have the old TZ
environment variable, which you have changed.
Once cron has kicked off a job, it doesn't have any further interest
in it so your only problem would be if there was a job scheduled to
start in the very short period whilst cron was not running. No way of
avoiding this: just check your crontabs, (/var/spool/cron/crontabs).
Simon Green
Altria ITSC Europe Ltd
AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
N.B. Unsolicited email from vendors will not be appreciated.
Please post all follow-ups to the list.
> From: Ken Sedlacek
> Sent: 23 October 2003 22:46
>
> I had thought about just killing it and letting it respawn, but I
> thought there should be a more eloquient way of doing this.
>
> Also, if by change cron was running a job at the time of the killing,
> it might be affected.
>
> There has to be a better way!
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:18 EDT