Re: cron has gone to UTC time?
On Sat, 6 Feb 1999, Steve Greenland wrote:
> On 30-Jan-99, 06:54 (GMT), "Mark W. Eichin" <eichin@thok.org> wrote:
> > I haven't seen the problem yet myself, but throw in an "env"
> > too... I've noted (in a bug report in regard to inetd) that doing
> > "apt-get upgrade" with sudo or su with a full *user* environment often
> > means that you end up with an incorrect environment for daemons that
> > get upgraded -- cron is vulnerable to the same bug, and probably
> > amenable to a similar fix: use
> > env - TZ=$(cat /etc/timezone) PATH=/sbin start-stop-daemon ... cron
> > instead of just using start-stop-daemon...
>
> After looking at the source code, and playing around a little, I suspect
> that this is the root of the problem. I hesitate to throw Mark's
> proposed fix in at this point in slink, and it's more of a fragility
> thing than a bug, and it's easily fixed (restart cron), but only if it's
> noticed.
Considering that at least on my system there is no 'TZ' variable exported
by my user I do not think this explains my problem, but it is
none-the-less a problem (BTW using no timezone is probably better than one
from etc)
Jason
Reply to: