Under z/VM. I used the ntpdate command that Christian posted and also eyeballed them.
zlnx168 is recently rebooted and is not running ntp. zlnx169 is zlnx168:~ # ntpdate -qv zlnx169 27 Jul 09:21:21 ntpdate[4014]: ntpdate [email protected] Mon Jun 6 08:19:21 UTC 2016 (1) server 10.93.15.169, stratum 5, offset 0.003511, delay 0.02582 27 Jul 09:21:27 ntpdate[4014]: adjust time server 10.93.15.169 offset 0.003511 sec zlnx168:~ # uptime 09:21am up 0:03, 2 users, load average: 0.13, 0.16, 0.07 zlnx168:~ # ps -ef | grep ntp root 4019 3975 0 09:21 pts/0 00:00:00 grep ntp -----Original Message----- From: Martin Schwidefsky [mailto:[email protected]] Sent: Wednesday, July 27, 2016 1:17 AM To: Linux on 390 Port Cc: Cortes, Marcy D. Subject: Re: Back to the future? On Tue, 26 Jul 2016 17:33:31 +0000 Marcy Cortes <[email protected]> wrote: > Martin wrote: > > >Either the sysadmin or NTP should do this, otherwise the system clock will > >be off by 26 seconds (soon 27 seconds as another leap second is scheduled). > > This kind of implies that if I disable NTP on a server and reboot, it should > be 26 seconds or so off. > It's not. I'm seeing .003590 offset on one I just tried. LPAR or z/VM? I just tried as well and I do get the 26 second offset for both LPAR and z/VM. How did you get the timestamps you are comparing? -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
