diff options
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ | 12 |
1 files changed, 7 insertions, 5 deletions
@@ -1116,7 +1116,8 @@ look at the file `login/README.utmpd'. defined). Instead GNU libc contains zone database support and compatibility code for -POSIX TZ environment variable handling. +POSIX TZ environment variable handling. For former is very much preferred +(see question 4.3). 3.4. The prototypes for `connect', `accept', `getsockopt', @@ -1407,7 +1408,8 @@ functions are not implemented. {UD} The problem is that people still use the braindamaged POSIX method to select the timezone using the TZ environment variable with a format EST5EDT -or whatever. People, read the POSIX standard, the implemented behaviour is +or whatever. People, if you insist on using TZ instead of the timezone +database (see below), read the POSIX standard, the implemented behaviour is correct! What you see is in fact the result of the decisions made while POSIX.1 was created. We've only implemented the handling of TZ this way to be POSIX compliant. It is not really meant to be used. @@ -1416,9 +1418,9 @@ The alternative approach to handle timezones which is implemented is the correct one to use: use the timezone database. This avoids all the problems the POSIX method has plus it is much easier to use. Simply run the tzselect shell script, answer the question and use the name printed in the end by -making a symlink to /usr/share/zoneinfo/NAME (NAME is the returned value -from tzselect) from the file /etc/localtime. That's all. You never again -have to worry. +making a symlink /etc/localtime pointing to /usr/share/zoneinfo/NAME (NAME +is the returned value from tzselect). That's all. You never again have to +worry. So, please avoid sending bug reports about time related problems if you use the POSIX method and you have not verified something is really broken by |