Path: utzoo!attcan!uunet!know!sdd.hp.com!usc!ucsd!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) Newsgroups: comp.sys.apollo Subject: re: Date and other wierd problems on an Apollo Dn4500 running Sr10.1 Message-ID: <9010261958.AA13955@pan.ssec.honeywell.com> Date: 26 Oct 90 19:58:14 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 43 > <> > In article <9010260403.AA11351@pan.ssec.honeywell.com>, thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) writes: > (I think). YOu can use offsets with 30 minute increments as well (e.g. -4:30) > if you have weird or funky timezones, and you can even NAME your time zone so > that the machine calls it by your (up to 4 letter) name. > > The 30-minute increment thing is (in my opinion) a bug in > cal_$decode_ascii_tzdif(), which is in kslib. The author of this routine > has a very small airplane and has never flown it as far away as Nepal or any > of the other countries that are not on 30-minute timezones. Now that we > have all those troops in Saudi, where time zones are on one minute > increments, it might be time to fix this. Well, I can't be too hard on the author. I have never encountered a 30-minute offset, let alone a 1-minute one! (I guess that says I'm just a poor country hick from the Midwest. :-) > You can get around this by calling the os routine cal_$write_timezone() > directly. The os stores time zones on disk in one minute increments. > > By the way, it isn't immediately apparent, but you must reboot after > resetting the time zone. Huh??? We have never re-booted after setting time zone. In fact, I played around with it when I was writing my original reply, and had no problems. I believe you're mistaken on that count. > Also, why do you have to be root to set the time, but anyone can set the > time zone? Probably because setting the time has a direct effect on the O/S, while the time zone does not. Incidentally, you can fake the Apollos out and modify the date (through Aegis) even if you aren't root. Just run 'calendar' and say you have no disk. The adjusted time will still be recorded onto the disk when a shutdown occurs. (Note that this _does_ require a shutdown to take effect. Unlike the Unix 'date' (as root) command.) John Thompson (jt) Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com As ever, my opinions do not necessarily agree with Honeywell's or reality's. (Honeywell's do not necessarily agree with mine or reality's, either)