brownfld@ux1.cso.uiuc.edu (10/13/90)
At the NeXT here where I work, we have a crontab.local set up for
various functions (hourly chimes, access restrictions during operating hours,
etc.) But it hasn't been working correctly.
If I try to set the date for Central Daylight Time, I do the following
from root:
date -d1 -t360 whatevertimeit.is
This returns the timezone WET. I can't get date to display CDT time,
even though the actual numerical value under CST is correct. At 6:00pm,
crontab.local executes a shell that tells everyone we're closing (sndplay.)
This action occurs at 8pm, and everything else in crontab.local goes off
two hours later. The date is numericaly correct, but the timezone seems
to be messing up. Preferences gives me an error when I try to change the
timezone (failure to write, something like that.)
Does anyone know why the date is messed up? We're running NextStep 1.0
on the original Cube, with a very standard setup. Thanks a lot for any help
and advice.
Ken.
Kenneth R. Brownfield ken-b@uiuc.edu
University of Illinois, Urbana-Champaign
Junior, Computer Science/Engineering.