Tim wrote: > > Headers from your email, as I received it (but abbreviated), below: > > Received: from localhost; Mon, 28 Dec 2009 16:13:43 +1030 > Envelope-to: tim@localhost; Delivery-date: Mon, 28 Dec 2009 16:27:35 +1100 > Received: from server for tim@localhost (single-drop); Mon, 28 Dec 2009 16:13:43 +1030 (CST) > Received: from mx1-phx2.redhat.com by external mail ; Mon, 28 Dec 2009 16:27:35 +1100 > Received: from lists01.pubmisc.prod.ext.phx2.redhat.com ; Mon, 28 Dec 2009 00:20:06 -0500 > Received: from int-mx05.intmail.prod.int.phx2.redhat.com ; Mon, 28 Dec 2009 00:17:02 -0500 > Received: from mx1.redhat.com ; Mon, 28 Dec 2009 00:16:57 -0500 > Received: from s3.sapience.com ; Mon, 28 Dec 2009 00:16:46 -0500 > Received: from mail.prv.sapience.com ; Mon, 28 Dec 2009 00:16:45 -0500 > Received: from lap1.prv.sapience.com ; Mon, 28 Dec 2009 00:16:45 -0500 > > I can see a delay in the middle, but only a few minutes. That could > well be normal processing times. > > And something odd within my LAN; some 14 minutes going back and forth in > time. All our PCs are NTP synchronised, and timezones are set right > (Adelaide, South Australia), so it's not a local clock issue. > > You say it isn't a local clock issue, yet the time zones are flipping within your LAN. AFAIK, Adelaide is GMT+1030 in summer time. The only time I've seen time zone incorrectness like this was when some systems, at the office I worked at, had some UID's that would alter the TZ environment variable. Made troubleshooting time sensitive transactions a real bitch. I'm especially not fond of systems that use alpha designations for time zones. CST, is that "Central Standard Time (USA)", "China Standard Time", or ? :-)
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
