Linux date as filepro sees it

[Jay R. Ashworth]

On Thu, Oct 26, 2006 at 04:26:15AM -0700, Jeff Harrison wrote:
> Thanks Mark, Bill and Ron for all of the suggestions. 
> I'll give this info to their sys admin as I am not
> brave enough to do any of this remotely.  - Or perhaps
> I should say I am not remotely brave enough :-)

Hee.

That's me, and that machine is *supposed* to already be running NTP...

and it is:

===
ntpdc> peers
remote           local      st poll reach  delay   offset    disp
=======================================================================
*ns1.dns.pciwest 192.168.116.11   2 1024  377 0.11433  0.010257 0.01482
=LOCAL(0)        127.0.0.1       10   64  377 0.00000  0.000000 0.00096
=a1.develooper.c 192.168.116.11   3 1024  377 0.09695  0.011883 0.01482
=pojo.biz        192.168.116.11   2 1024  377 0.07620  0.015860 0.01483
ntpdc> techspec:~ # date
Thu Oct 26 09:49:06 EDT 2006
===

SO it must be timezone.  If TZ is empty, it certainly is.

To recap: *nix boxen all maintain system time in UTC (if they're
administered properly), even if the hardware clock on the box is local;
the TZ variable tells the output routines how far to adjust that time
to display it in local time.  TZ should, IIRC, be "EST5EDT" in our time
zone.

I'm not aware of that having changed since Christ was, at least, a
Sergeant.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

	"That's women for you; you divorce them, and 10 years later,
	  they stop having sex with you."  -- Jennifer Crusie; _Fast_Women_