Re: SL 7.2 on a HP Zbook

2016-10-17 Thread Bill Askew
Hi Yasha
It is a Zbook 15 G2.
Ken and Mark put me on the right path.
We use our laptops unconnected to any networks.  Previous to RHEL 7 the system 
clock was saved to the hardware clock on shutdown or reboot by default. However 
NTP does sync the system and hardware clocks.  Since we do not use NTP no 
synchronization happens.
-Bill
--
On 10/07/2016 11:14 AM, Bill Askew wrote:
> Hi everyone
> I am using SL 7.2 on a HP Zbook.  So far the only issue that I have is 
> setting the date and time does not set the Zbook's hardware clock.  It does 
> change the time for the duration of the session but when the ZBook is 
> rebooted the time goes back to what it was before plus the amount of time I 
> spent during the session.
> Does anyone have a fix for this?
> Thanks

I am using SL 7.2x on a HP Zbook without this issue.  Which model?  Mine 
is several years old and thus might be different from yours.

Yasha Karant


Re: SL 7.2 on a HP Zbook

2016-10-13 Thread Yasha Karant

On 10/07/2016 11:14 AM, Bill Askew wrote:

Hi everyone
I am using SL 7.2 on a HP Zbook.  So far the only issue that I have is setting 
the date and time does not set the Zbook's hardware clock.  It does change the 
time for the duration of the session but when the ZBook is rebooted the time 
goes back to what it was before plus the amount of time I spent during the 
session.
Does anyone have a fix for this?
Thanks


I am using SL 7.2x on a HP Zbook without this issue.  Which model?  Mine 
is several years old and thus might be different from yours.


Yasha Karant


Re: SL 7.2 on a HP Zbook

2016-10-07 Thread Ken Teh

If you grep'd the rc init files for hwclock, you will find it in halt.  You 
can't grep systemd.  All you can do is read the man page and there's a lot of 
man pages to read.  :(






On 10/07/2016 01:28 PM, stod...@pelletron.comwrote:

- Original Message -
From: "Bill Askew" 
To: scientific-linux-us...@listserv.fnal.gov
Sent: Friday, October 7, 2016 1:14:04 PM
Subject: SL 7.2 on a HP Zbook

Hi everyone
I am using SL 7.2 on a HP Zbook.  So far the only issue that I have is setting 
the date and time does not set the Zbook's hardware clock.  It does change the 
time for the duration of the session but when the ZBook is rebooted the time 
goes back to what it was before plus the amount of time I spent during the 
session.
Does anyone have a fix for this?
Thanks

There is probably a more "systemd" type method, but this as root has always 
worked:
hwclock --systohc



Re: SL 7.2 on a HP Zbook

2016-10-07 Thread Mark Stodola

On 10/07/2016 02:09 PM, Bill Askew wrote:

Mark
The hwclock --systohc worked thanks!  :-)

Still kind of odd that the date command does not cause the date and time to the 
hardware clock when shutting down
(this is how it works on a Lenovo T61p running SL 6.2)

Bill



This is probably useful:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-hwclock.html

There is a note about how the system clock is synced every 11 minutes to 
hardware.  This might be a configuration option in chrony or ntpd. 
Plenty of good information in that document to dig through.


Re: SL 7.2 on a HP Zbook

2016-10-07 Thread Bill Askew
Mark
The hwclock --systohc worked thanks!  :-)

Still kind of odd that the date command does not cause the date and time to the 
hardware clock when shutting down 
(this is how it works on a Lenovo T61p running SL 6.2)

Bill


Re: SL 7.2 on a HP Zbook

2016-10-07 Thread stod...@pelletron.com
- Original Message -
From: "Bill Askew" 
To: scientific-linux-us...@listserv.fnal.gov
Sent: Friday, October 7, 2016 1:14:04 PM
Subject: SL 7.2 on a HP Zbook

Hi everyone
I am using SL 7.2 on a HP Zbook.  So far the only issue that I have is setting 
the date and time does not set the Zbook's hardware clock.  It does change the 
time for the duration of the session but when the ZBook is rebooted the time 
goes back to what it was before plus the amount of time I spent during the 
session.
Does anyone have a fix for this?
Thanks

There is probably a more "systemd" type method, but this as root has always 
worked:
hwclock --systohc