To my knowledge, hwclock has never been updated to understand mainframe clocks. In your position, I would probably just change the timezone to be GMT, and then counsel your client as to all the very good reasons why their system clock should be set to GMT, and not local time.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 11:07 PM To: [EMAIL PROTECTED] Subject: Changing Timezone Offset without reinstalling Hi all... We have a Linux image (SLES 8 under z/VM 4.4) that has a time/date problem. The system hardware clock on the processor runs LOCAL time; the timezone offsets in the SYSTEM CONFIG file are zero; and the VM time is correct -- local time. When installing SLES 8, the user specified the correct timezone (US/Mountain) and that the hardware clock was running local time. But the time displayed after installation is 7 hours off. We've double checked that the hardware clock is local time; the VM offsets are zero; and that SLES 8 was installed specifying that the hardware clock was local time. But the time is still wrong. Poking around it seems that /etc/sysconfig/clock seems like it would control that. Ours said: HWCLOCK="--localtime" TIMEZONE="US/Mountain" But changing to HWCLOCK="-u" (based on the comments in the file) made no difference, even after rebooting... 1) Short of reinstalling from scratch, is there somewhere else to change the clock offset? 2) Any thoughts why specifying that the hardware clock was on local time "didn't work" as expected? Thanks for any thoughts... Lee Stewart Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
