We are connecting to external NTP server for ESX Hosts. All VMs are sychronized with the ESX Hosts via set up in VMWare Tools.
Howerver, a fellow suggests that we should also synchronize the time with BIOS Clock.
We would like to know
1) Why we have to do so ?
2) What is the command to be used ?
Thanks
Because the bios is not synchronized with anything. You set it in the bios and it keeps time by the battery. The sync is just like in windows computers. You set the time in Windows and it keeps the BIOS clock in sync incase the battery is low, etc
Hi,
It is exactly the command he suggests to run.
As you have mentioned, the BIOS clock should be synchronized by itself, why does VMWare still recommends running that command OR local hardware clock <> BIOS clock ?
Thanks
Message was edited by: TonyJK
Because the bios is not synchronized with anything. You set it in the bios and it keeps time by the battery. The sync is just like in windows computers. You set the time in Windows and it keeps the BIOS clock in sync incase the battery is low, etc
Hello,
There is nothing more you need to do.
The rc0.d shutdown/reboot runlevel will sync the NTP sync'd running clock to the RTC hardware clock.
So it always sets the hardware clock to the last sync'd value when shutting down or rebooting.
Here is the actual script that is run
crond Start/Stop the cron clock daemon.
sync_hwclock() {
. /etc/sysconfig/clock
convert old style clock config to new values
action $"Syncing hardware clock to system time" /sbin/hwclock $CLOCKFLAGS
[ "$SYNC_HWCLOCK" = "yes" ] && sync_hwclock
Sync the system clock.
. /etc/sysconfig/clock
convert old style clock config to new values
runcmd $"Syncing hardware clock to system time" /sbin/hwclock --directisa $CLOCKFLAGS