Hello mark,

On 02 Dec 12 at 13:33, you wrote to me:

 ml>> well, it has one TZUTC but it is incorrect if you are at -6 and
 ml>> your local clock is also running -6...

 NB>> I've already asked as to why it's setting my TZUTC kludge to
 NB>> 0000, since Golded appended the correct one.

 ml> how does golded know about the right one? the software i'm familiar
 ml> with uses the TZUTC environment variable... set it to the proper entry
 ml> for the local clock and then run your program(s)...

It must read my system clock, which uses UTC, whereas (I got the answer
from Rob) Synchronet has a setting for Local Time. If you select any USA
timezone, ie: CDT or CST -- which I am in, It seems to give the TZUTC 0000
kludge. This post should be fixed, as I changed Synchronet to UTC -0600.
Maybe I found a bug, I don't know. He hasn't responded to me a second time
yet.

 ml> FWIW: one of the programs i speak of above introduced TZUTC to the
 ml> world ;)

 NB>> I've looked over Sync's configuration a few times now, and don't
 NB>> see anything about a TZUTC kludge, unfortunately. I'll just have
 NB>> to be patient on that the answer to this one. :(

 ml> i haven't seen anything in the synchronet echo(s) about it...

I don't usually bug report there. If I can catch him on IRC in a lot
shorter of a timespan, I'll ask him there.. rather than waiting hours for
an answer.

Regards,
Nick

--- SBBSecho 2.20-Linux