Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!UM.CC.UMICH.EDU!Pat_McGregor From: Pat_McGregor@UM.CC.UMICH.EDU Newsgroups: comp.sys.apollo Subject: mailer daemon mail Message-ID: <3268562@um.cc.umich.edu> Date: 28 Jul 88 19:17:38 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 80 This message was forwarded to the Postmasters at The University of Michigan due to a problem with our name server. It's possible that some or all or you may have already received this message, but we wanted to forward it on to you in case your copy got eaten. ---(Forwarded from: mtv@umix.cc.umich.edu, Dated: Tue, 26 Jul 88 17:41:32 EDT)--- Return-path: Received: from umix.cc.umich.edu by um.cc.umich.edu via UMnet; Tue, 26 Jul 88 17:29:48 EDT Received: by umix.cc.umich.edu id AA02505; Tue, 26 Jul 88 17:41:32 EDT Date: Tue, 26 Jul 88 17:41:32 EDT From: mtv@umix.cc.umich.edu Message-Id: <8807262141.AA02505@umix.cc.umich.edu> To: postmaster@um.cc.umich.edu Received: by umix.cc.umich.edu (5.54/umix-2.0) id AA11369; Tue, 26 Jul 88 11:55:52 EDT Received: from umix.cc.umich.edu by mailrus.cc.umich.edu (5.59/1.0) id AA01360; Tue, 26 Jul 88 11:44:41 EDT Date: Tue, 26 Jul 88 11:44:41 EDT >From: Mailer-Daemon@mailrus.cc.umich.edu (Mail Delivery Subsystem) Subject: Returned mail: Host unknown Message-Id: <8807261544.AA01360@mailrus.cc.umich.edu> To: ----- Transcript of session follows ----- 550 mailgw.cc.umich.edu.internet... 550 Host unknown 550 ... Host unknown ----- Unsent message follows ----- Received: from umix.cc.umich.edu by mailrus.cc.umich.edu (5.59/1.0) id AA01358; Tue, 26 Jul 88 11:44:41 EDT Received: by umix.cc.umich.edu (5.54/umix-2.0) id AA11277; Tue, 26 Jul 88 11:50:47 EDT Date: Tue, 26 Jul 88 11:50:47 EDT >From: Mailer-Daemon@umix.cc.umich.edu (Mail Delivery Subsystem) Subject: Returned mail: Remote protocol error Message-Id: <8807261550.AA11277@umix.cc.umich.edu> To: ----- Transcript of session follows ----- >>> MAIL From: <<< 554 rewrite: cannot prescan canonical hostname: 554 post-apollo@ucbvax.berkeley.edu... Remote protocol error: Bad file number ----- Unsent message follows ----- Received: by umix.cc.umich.edu (5.54/umix-2.0) id AA11275; Tue, 26 Jul 88 11:50:47 EDT Received: by a.cc.umich.edu (5.59/1.0) id AA01293; Tue, 26 Jul 88 11:31:51 EDT >From: rees@a.cc.umich.edu (Jim Rees) Message-Id: <8807261531.AA01293@a.cc.umich.edu> Date: Tue, 26 Jul 88 11:16:15 EDT Subject: Re: Calendar sync To: mcdonald@loki.hac.com Cc: apollo@umix.cc.umich.edu Reply-To: rees@caen.engin.umich.edu (Jim Rees) In-Reply-To: mcdonald@loki.hac.com, Mon, 25 Jul 88 15:47:15 pdt Does anyone know of a good way to keep all the calendars on an apollo network in sync? I do not want to shut down a node to rest the onboard clock. I would like to, from one node, start a job that hops from node to node to set the clock to the correct time. At sr10, you can reset the node time without shutting down. If you don't have sr10, you can't. I think you can get a daemon that synchronizes clocks for you. If not, it would be pretty easy to write. You need one or more central nodes, preferably with a WWV clock, running a time of day server. There's an RFC out on this (don't know the number). There is nothing worse than seeing a network where one node thinks it is 8:00 am PST July 25, 1988 and another thinks it is 9:00 pm PDT July 21, 1988. The timezone is a little trickier. It's stored in a completely separate way. Unfortunately, I think you still need to shut down to change the timezone, even at sr10. This is a lot better than Unix in the old days, which required you to recompile all your programs to change the timezone. -------