Hi,
On 2015-10-15 15:48:40, Janis Kracht wrote to Wilfred van Velzen:
about: "Re: it is still wrong even if it appears right":
JK> @TZUTC: -0500
>> And we were talking about the TZUTC kludge in messages from Janis, who
>> uses BBBS on Linux. So BBBS should be able to use that. I don't know if
>> it does, bu if it does, something goes wrong. ;)
JK> AFAICS, BBBS is handling it just fine... do you see something differently
JK> there from this system?
It says -0500, which is only right for winter-time for your timezone. Now,
during DST it should be -0400.
JK> I don't do anything with the TZ here in the script that runs nodes 1-3
JK> of bbbs (1 phone modem, 2 & 3 are dialout nodes) , but the system time
JK> here is correct for where I live:
JK> ~$ date
JK> Thu Oct 15 15:38:41 EDT 2015
JK> I expect BBBS would grab that, but I can check with Kim about it. I mean
I
JK> can put a TZ=??? statement in the 3 nodes that I run for dialout to other
JK> nodes, but that won't affect nodes that bbbs spawns for incoming calls. I
JK> can also check what I have in the config for the other nodes (4-15), but
JK> nothing would have changed with that since I set them up.
You don't need to set TZ on Linux or Windows. If you set the correct timezone
during system installation the OS knows what your offset to UTC is at all
times. If software queries the OS in the right way, it can generate the correct
TZUTC kludge. Like in this message where golded does this.
Bye, Wilfred.
--- FMail-W32-1.69.11.142-B20151009
* Origin: Native IPv6 connectable node (2:280/464)
|