We just went through this here as well. One of my colleagues (Dan Leonard) actually did the leg-work on this and deserves credit - but here's what he came up with (note: 238 identifies one of our Linux/390 systems):
OK, here's the deal: tzselect sets the variable TZ to the time zone you select; great for a per session or per user basis, but not quite "global" enough. On further investigation, I found that time is modified with the /etc/localtime file, which on 238 was s-linked to /usr/share/zoneinfo/EDT. That file does not exist on 238. I changed the /etc/localtime link to point to /usr/share/zoneinfo/EST5EDT, and all is well, at least for my purposes. Let me know if anybody experiences any problems. Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6527 1111 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-3123 [EMAIL PROTECTED] -----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 2:03 PM To: [EMAIL PROTECTED] Subject: Re: What Time Is It? The Linux/390 guest gets its initial time setting from the underlying VM system at IPL time. I would look to see if the other guests are running something like NTP, and the "problem" guest is not. Mark Post -----Original Message----- From: Scully, William [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 12:59 PM To: [EMAIL PROTECTED] Subject: What Time Is It? At CA we run several Linux guests. One, in particular, is confusing me. The date command response is "way off", both in hours and minutes. When I correct it (by using the Linux date command) and restart (perhaps a week later) the date command's response is, again, way off. And when it's wrong it's never wrong by the same amount of time. None of our other SuSE 2.4 servers is acting like this. Where should I look to fix this? William P. Scully Systems Programmer Computer Associates International, Inc 2291 Wood Oak Drive Unit 5-29C Herndon, Virginia 20171 Work: +1 703 708 3976 [EMAIL PROTECTED]
