When we had linux on Z, we ran the ntpdate program once per day (before start of
business). On our current ESX and Oracle Virtualization (xen), we need to run
it every hour.
/Tom Kern
On 6/4/2012 12:31, David Boyes wrote:
> Running NTP everywhere wakes every guest up periodically, so you waste a
On Jun 4, 2012, at 11:23 AM, Dean, David (I/S) wrote:
> Amen. We run it on 60 plus servers, started because of a tie in to Active
> Directory on about 4 servers, but continued it on all servers solely to work
> and play well with others.
I had this requirement and found it sufficient to run
Excluding Marcy, of course.
-Original Message-
From: Dean, David (I/S)
Sent: Monday, June 04, 2012 2:23 PM
To: 'Linux on 390 Port'
Subject: RE: Run NTP on zLinux or not?
Amen. We run it on 60 plus servers, started because of a tie in to Active
Directory on about 4 servers, but continue
Amen. We run it on 60 plus servers, started because of a tie in to Active
Directory on about 4 servers, but continued it on all servers solely to work
and play well with others. I am 54 years old and come from a complete Window's
background 1980-2003, not becoming a "convert" (partial) until 2
> Not running it is also one more
> way to make your z type of Linux "different" from the x type of Linux. We
> really don't need any more of those.
> Marcy
Yeah. What she said.
--
For LINUX-390 subscribe / signoff / archive a
We run it. It is required by our Kerberos based authentication system and it
is required by our security rules.
It doesn't seem to take a lot of resources. Not running it is also one more
way to make your z type of Linux "different" from the x type of Linux. We
really don't need any more of
> > The things that really care about time (like any service using Kerberos
> security, or other things that use time as a salt in some other process) need
> NTP because they don't work without completely accurate time.
> > Everything else can get along fine with running ntpdate once a day.
>
> II
On Mon, Jun 4, 2012 at 6:31 PM, David Boyes wrote:
> The things that really care about time (like any service using Kerberos
> security, or other things that use time as a salt in some other process) need
> NTP because they don't work without completely accurate time.
> Everything else can get
On Mon, Jun 4, 2012 at 6:08 PM, Scott Rohling wrote:
> Was having a conversation today about running Linux on System z and whether
> it needed to run an NTP client -- the statement being STP is used to keep
> the mainframe time in synch, so why run NTP on a Linux guest - the system
> time is corr
Running NTP everywhere wakes every guest up periodically, so you waste a fair
amount of cycles waking up to do nothing for most guests.
The clocks in Linux guests do drift slightly (even if the HW is synced to STP)
-- it's order of tenths of microseconds, but it does lose a little (barely
meas
I have a vague memory that Linux on z does not use the "timer tick" that some
other platforms use. That it uses the z's hardware clock for timing. I think it
was the "tickless kernel"? But I don't have a Linux on z system here anymore.
Even without STP, the hardware clock is very accurate. I don
Recommendation leans toward "no", but is not firm.
Back before we had STP, I used to say "no", then changed my story to
"yes, run it". Lately not so sure.
6 or 7 or more years ago, the point was ... dozens or hundreds of
Linux guests ... do you want them all running NTP? At first, "we"
said no
Was having a conversation today about running Linux on System z and whether
it needed to run an NTP client -- the statement being STP is used to keep
the mainframe time in synch, so why run NTP on a Linux guest - the system
time is correct. My understanding is that Linux maintains it's own clock
s
13 matches
Mail list logo
