Subj : Date/Time in Messages
To : Scott Street
From : Vince Coen
Date : Tue Apr 17 2012 08:58 pm
Hello Scott!
16 Apr 12 21:42, you wrote to :
>> Looking at my msg I can not see any TZUTC setting which might
>> explain it.
> Aren't you already on UTC? :)
Yep but I used to have some king of setting for it even if only for this time
of year when its set as TZUTC=0100
May be it went redundant when I switched from OS/2 and Maximus to Linux and
mbse?
Just cannot remember, and I'm only 65 in June.
That does start to worry me :)
>> * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)
> Just figuring based on your location in nodelist.
> If your system's timezone is already UTC - then TZUTC would be
> redundant.
Yep, but see above!
> But Fidonet has been broken ever since the first message layout was
> specified as local time being transmitted. It should have NEVER been
> local time transmitted, but UTC (GMT then) always. Whether or not the
> time stored in the local message base was UTC or local should have
> been up to the implementer of the software.
> I digress... message time is a network wide issue, the TZUTC is a
> kludge that is ignored on most software end-points anyway. I should
> propose a FTSC change to move to UTC time in all messages during
> transport, leaving the local storage up to the implementers.
As I said it was in use on the old MSDos based s/w, can't recall is used in
windows but would guess yes.
Must have a look through the docs for mbse and see if there is any mention of
it as its been years since doing so.
The system is more or less fully automated, just as well as I run multiple
services on same box such as httpd, Ftp, Mysql, Postgres, DB/2 servers as well
as MS sql 2008 and Oracle in seperate VMs (under VirualBox but only run when
required).
Not bad with a E6600 cpu and 6Gb Ram.
Vince
--- Linux/Mbse/GoldED+/LNX 1.1.5
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)
