I thought about timesyncing our MP3000 with ntp. Sounded doable. OS/2 is just another operating system. I could sync the clock there.
But the problem was that I needed to IPL VM, in order for VM to recheck the clock again. Not a good option for us. I then thought about creating "timezone" offsets that are in minutes and seconds. But there are too many cautions about changing the clock and VM's scheduling. I never got a feel for how long it would take the CP Scheduler to settle down when the clock was changed. If it took a few hours, I could live with it. 2 to 5 in the morning, I'm not too concerned with having an efficient scheduler. Just as long as it "gets better" by first shift. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 06/02 7:52 AM >>> So run the server and sync the rest of your network to VM ;-) Souunds like the way the world should be working anyway. Vic Cross wrote: > > On Fri, 30 May 2003, Steven A. Adams wrote: > > > I am being told that there is not a way to use ntpd under one of my > > Linux guests to set the clock and propagate these settings through VM to > > the CTC. > > We have a bunch of Linux guests doing time sync over Guest LAN directly to > an NTP server out on the 'real LAN'. This works fine. > > If you're trying to sync VM's time to NTP, I don't know of a way to do > that. There is an NTP *server* for VM on the IBM VM downloads page, but I > suspect this does not set VM's time. > > Cheers, > Vic
