Hi there,
I've run into a strange issue: I can't set the date (well, mostly the year) on my Cube. I've tried via Preferences and using the date command (but that has the Y2K bug, can only set the year up to 1999). My Cube is losing time quite a bit so I thought ntp could help out but although it gets the data from the servers, in no way can it set the date afterwards. Has anyone else run into this? Am I missing some patch or another?
Yes, there is a Y2K patch for NeXTSTEP 3.3.
Go look in the file archives on this site for it.
according to the README that does seem to clear it, although I'd swear that patchlevel had been applied... weird.
If you set the date to the 31 december 1999, at 11:59pm and wait a little more than a minute, what is the date ?
Forget it, I reapplied the whole 3rd edition patch for CISC, despite it complaining it was already installed. All fine now, shows the current date after ntp updating it. Just another quirk 8)
Well, I'm finding that my NeXTSTEP 3.3 VMware config shows the correct time in Preferences.app, but when I run "date" from the command line, it shows an hour off.
Also, I'm having a hard time getting ntp configured... can you walk me through that?
The TIMEZONE files are probably out of date for your location. We went through this a few years ago on this board you can search for some of the details on how to update that.
As far as ntp the easy way just run
/usr/etc/ntp -sf <IP of NTP SERVER>
that should set you clock if run as root. You can add a cron to do that every hour if you want. You can set up ntpd to do this but it's just as easy to just use ntp.
-Mike
Added: Here is the topic
http://www.nextcomputers.org/forums/index.php?topic=669 (
http://www.nextcomputers.org/forums/index.php?topic=669)
Thanks - I now have a cron job set up on my NS3.3 and OS4.2 boxes, and I have updated the zoneinfo file as well.