Chris Buckley([EMAIL PROTECTED]) is reported to have said: > Hi, > > A very strange problem has cropped up on our Debian GNU/Linux 3.1 box this > morning. > > We have a crontab for a user scheduled to run at: > > 45 4 * * * /path/to/utils/script-executed.pl > 2>/path/to/logs/stdout-foobar.log > > The cron.log shows this file running at "04:45". > > Aug 22 04:45:01 nbxprodsgw01 /USR/SBIN/CRON[684]: (netbanx) CMD > (/path/to/utils/script-executed.pl > 2>/path/to/logs/SEB_batch_logs/stdout.log) > > HOWEVER, the cron does not actually run until 09:45. > I have witnessed this first hand this morning, tailing the cron.log and > seeing at 09:45 the process run, but the time being recorded as 04:45. > > I can't immediately see a problem. > > [EMAIL PROTECTED]:/var/log$ tzconfig > Your current time zone is set to Europe/London > > [EMAIL PROTECTED]:/var/log$ date > Wed Aug 22 10:02:44 BST 2007 > > The box is one which, unfortunately, I do not have root rights on - we > outsource a lot of our servers. What checks would I need to perform (given > my limited user rights) to assess and help diagnose what the problem is? > > Any help very much appreciated.
Just found the same thing here. Had to run dpkg-reconfigure tzdata. It had me in Central Europe. :-( Wayne -- Beta. Software undergoes beta testing shortly before it's released. Beta is Latin for "still doesn't work." _______________________________________________________ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
