Re: Back to the future?

That's my speculation at the moment... that perhaps we need to jerk it back quickly before the applications start to get them closer together sooner rather than later. The app team is still researching how often they see this and if they can find a pattern. There are a couple of dozen servers

Re: Back to the future?

>>> On 7/25/2016 at 06:46 PM, Marcy Cortes >>> wrote: > Answering my own post. > The latter HWCLOCK option is not for s390x (the code in /etc/init.d/ntp > ignores it if set if s390* ) > > But the former might be a good thing. > On the handful of test servers I

Re: Back to the future?

Yes, when your hardware clock is not managed by NTP you cannot rely on it to accurately initialize the system clock on boot, so you should force an NTP clock sync ("jump") on startup. Otherwise the NTP smooth clock adjustment could take quite a while to get the system clock synced. Once the

Re: Back to the future?

Answering my own post. The latter HWCLOCK option is not for s390x (the code in /etc/init.d/ntp ignores it if set if s390* ) But the former might be a good thing. On the handful of test servers I ran it on, it gave me a smaller offset as queried with Christian's ntpdate command (10ths of

Re: Back to the future?

I don't think my problem is leap seconds. I'm talking maybe a second difference max between 2 linux servers (on z). We need to be accurate to the millisecond level. I see this in /etc/sysconfig/ntp ## Type: boolean ## Default:"no" # # Force time synchronization befor start

Re: Back to the future?

Hi, I'm not entirely sure I'm reading this right. Having just read up on how both STP, NTP, and POSIX deal with leap seconds, it would appear to me that all these systems track leap seconds and thus as a general rule represent a time approaching the formal UTC time. The precise mechanisms used

Xmas in July -- encryption

For those of us that are interested in encryption, there is a new package available on the IBM VM download page called KM. It's a CSL interface to the Cipher Message (KMxxx) instructions found on newer hardware. Included are some Rexx Pipelines stages for encrypting records flowing through a

Re: Back to the future?

I think I failed to mention we are running NTP and the servers where they are doing subtraction of timestamps to get deadlines are all zLinux. Without NTP things fall apart quickly here. Maybe things are being steered at the same rate? Or it's off so much at boot time due to the leap seconds

Re: Back to the future?

In a heterogeneous environment if your non Z NTP systems are off by roughly 26 seconds compared to your STP managed Z Linux clocks it could be due to this: https://access.redhat.com/articles/15145 basically - the default Linux timezone files do not respect leap seconds, but the long time

SHARE Atlanta - Request for Chairs

We have entered the home stretch. Those of you heading to SHARE will be arriving this weekend. We still have a need to fill some session Chairs, and who better to fill those slots than those of you going. Now is not the time to be shy, and definitely not the time to keep procrastinating. Now is