Not to be too pedantic, but the hardware clock on a 390 CAN be changed from software, without human intervention. It's just that 99.99% of the time it isn't a smart thing to do. (As in, how many interesting ways would you like to see your OS crash!)
> -----Original Message----- > From: David Boyes [SMTP:[EMAIL PROTECTED] > Sent: Friday, January 16, 2004 4:16 PM > To: [EMAIL PROTECTED] > Subject: Re: Setting Clock Time > > You cannot set the real HW clock on a 390 from Linux (or any other OS) > without human intervention at the physical processor console to enable > access to the clock hardware. The hardware is designed to work that way, > and > Linux can't change it. > > Linux gets it's initial date from the HW clock at boot and never consults > it > again. For the reason listed above, trying to store a value to the HW > clock > isn't really very useful, and there's no point in trying. > Use date or NTP. If you have more than one system, you should be using NTP > anyway to synchronize them all to the same time and keep them that way. > > NTP constantly adjusts the time on all participating machines so that all > machines are within a small delta of the same time. This is important for > lots of authentication stuff. > > > -- db > > David Boyes > Sine Nomine Associates > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > > Leonardo Rodriguez > > Sent: Friday, January 16, 2004 4:04 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Setting Clock Time > > > > > > The problem with the date command is that I have read that > > this command > > doesn't store > > the values at boot moment but the hwclock command does, is it true? ______________________________________________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on the basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
