Anyone got the time?

[Flash]

Can anyone definitively tell me when/on what occasions panther and tiger clients do time lookups? Lookups don’t seem to occur at startup or login, only when forced from Date & Time pane. No problem doing a successful ntptrace in Terminal.

A cron job to force time lookups probably won’t work – think about it…

Will tiger clients bound to OD do lookups upon login? This is a nice feature on Windows clients bound to an AD.

[Flash]

My iBook/Powerbook users frequently drain their batteries and the date goes back to 1970. It will stay this way indefinitely, until an admin logs in and either forces a lookup or manually sets the date and time. ntpd is in fact running, but never does a lookup. Ideas?

[Anonymous]

[QUOTE BY= Flash] My iBook/Powerbook users frequently drain their batteries and the date goes back to 1970. It will stay this way indefinitely, until an admin logs in and either forces a lookup or manually sets the date and time. ntpd is in fact running, but never does a lookup. Ideas?[/QUOTE]

Same here. Our PowerBook users let their batteries drain while on the road, date/time goes back to groovy 1969. What’s not so groovy is when their Entourage reminders don’t pop up anymore.

Connecting to various networks will not reset the time, only authenticating as admin in the Date & Time System Pref will force it to do a lookup. This affects PowerBooks running 10.3.6 – 10.4.2.

[Flash]

OK, I’ll buy that. ntpd man indicates that “-g” is the magic switch that will jerk client time back to current immediately. However, I cannot find where the system starts ntpd to add the switch. Is there a lanchd.conf?

[Author]

Posts