AT job scheduled exactly 2 hours late

[bohunk24]

This occurs on an i386 box running Unix System V/386 Release 4.2 Ver 1.1.2.

I have an 'at' scheduling anomaly whose behavior I am trying to understand. On one particular system, when an 'at' job is submitted, the time the job is actually scheduled to run is exactly 2 hours later than what the command stipulated. I append the output that illustrates the problem:

-----------------------------
btd33m01!root[9] date
Fri May 13 09:19:42 EDT 2005
btd33m01!root[10] at 09:21
/test.sh

UX:at: WARNING: Commands will be executed using /usr/bin/sh
UX:at: INFO: Job 1115997660.a.0 at Fri May 13 11:21:00 2005
btd33m01!root[11]
-----------------------------

So, at 09:19:42 I submit the 'at' job to run at 09:21, and the system replies "OK, I'll run it at 11:21." The "consistently off by exactly 2 hours" symptom suggests to me some kind of timezone cause.
However, the TZ env var looks the same as the other related systems, none of which display this problem:
export TZ; TZ=':/usr/lib/locale/TZ/US/Eastern'

Entries in the crontab on that system, run at the correct time. So this symptom seems to affect only jobs submitted using 'at'.

Any explanation or suggestion on what else to look at?
Thanks!

 

[KenCunningham]

Is your export of TZ really before your TZ definition as it would appear from the above? Sorry if I've missed something here!

 

[bohunk24]

Ken - Thanks for the reply, but unfortunately that is not relevant to the problem. Once you have submitted a job with 'at', you can get the details of the job by typing at the command prompt:
at -d <job-id>
The environment variables that are set for the job's execution environment will be displayed like this:
export TZ; TZ=':/usr/lib/locale/TZ/US/Eastern'
It's simply a formatting convention used by 'at'.