Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!apple!uokmax!munnari.oz.au!bruce!merlin!ianh From: ianh@bhpmrl.oz.au (Ian Hoyle) Newsgroups: comp.sys.sgi Subject: problems setting the time Message-ID: Date: 7 Dec 90 06:10:38 GMT Sender: usenet@bhpmrl.oz.au (USEnet nntp account) Organization: BHP Melbourne Research Laboratories, AUSTRALIA Lines: 53 I'm having a few problems resetting the date/time on my 240GTX (Irix 3.3.1). We are running timed to keep our machines (4D/20 & an aging 4D/50) in sync, but because the clock had drifted I wanted to change the time. I tried using "date" and failed. I then used sysadm directly but again couldn't do it as is outlined below (my machine is called morgana). root @ morgana-> date Fri Dec 7 16:11:10 EST 1990 root @ morgana-> timedc timedc> msite master timedaemon runs on morgana timedc> quit and now the tail end of using sysadm to set the time ..... Current date and time: Fri. 12/07/90 16:11 Change the date and time? [y, n, ?, q] y Month default 12 (1-12): Day default 07 (1-31): Year default 90 (70-99): Hour default 16 (0-23): Minute default 11 (0-59): 02 Date and time will be set to: 12/07/90 16:02. OK? [y, n, q] y Fri Dec 7 16:02:00 EST 1990 The date and time are now changed. The cron has been restarted to pick up the new time and/or time zone. Press the RETURN key to see the syssetup menu [?, ^, q]: q root @ morgana-> root @ morgana-> date Fri Dec 7 16:12:06 EST 1990 AAAAAaaaaaaaargh, the date/time hasn't budged. :-( It looks like timed is preventing me resetting the clock. I would have thought that if I'm on the machine running as a master this would have been an allowed operation ?? ian -- Ian Hoyle /\/\ Image Processing & Data Analysis Group / / /\ BHP Melbourne Research Laboratories / / / \ 245 Wellington Rd, Mulgrave, 3170 / / / /\ \ AUSTRALIA \ \/ / / / \ / / / Phone : +61-3-560-7066 \/\/\/ FAX : +61-3-561-6709 E-mail : ianh@bhpmrl.oz.au