Daniel, No, and no. Linux/390 is not getting the time from sysplex timer (at least not directly). When Linux/390 boots up, it gets the time from VM (not the hardware). (In your case, VM does get the time from the timer.) After that, Linux/390 tries to keep the system time on its own. Which means it will drift. That's why I use NTP on my Linux/390 systems. I would not assume that the stratum of 10 = 0. I would assume that 10 = 10, meaning at the end of a long line of time servers. I'm guessing the comment is a typo.
Mark Post -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 3:49 PM To: [EMAIL PROTECTED] Subject: quick linux time (and NTP) question Running RH 7.2 in an LPAR. I wanted to verify something. Hardware is getting the time from a sysplex timer. Linux is getting the time from the hardware (how?). So, the "local clock" on my linux server is a reflection of the sysplex timer? Running an NTP server using the local clock as a server (127.127.1.0) is effectively using the sysplex timer as the ETR? Also, newbie alert. Looking at the /etc/ntp.conf provided by redhat, one line is "fudge 127.127.1.0 stratum 10", but the comments are: "... when no outside source of synchronized time is available. The default startum is usually 3, but in this case we elect to use stratum 0." So my question here is, is 10 = 0? Thanks all, ~ Daniel
