summaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-01-20 11:36:34 +0000
committerUlrich Drepper <drepper@redhat.com>1999-01-20 11:36:34 +0000
commit8b4a471567e67f575c4582854d7688d36b348ec9 (patch)
tree0da867e96b55e6e0e45a0fbf1a7bda0d1271784e /FAQ.in
parent5d003fb2ea209009d1054cc924986f0ba46f1e8e (diff)
downloadglibc-8b4a471567e67f575c4582854d7688d36b348ec9.tar.gz
Update.
1999-01-20 Ulrich Drepper <drepper@cygnus.com> * sysdeps/unix/sysv/linux/vfork.c: Once again use generic version.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in14
1 files changed, 8 insertions, 6 deletions
diff --git a/FAQ.in b/FAQ.in
index 3635e7e95e..0af71454d4 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -932,7 +932,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 ?tzdb).
?? The prototypes for `connect', `accept', `getsockopt',
`setsockopt', `getsockname', `getpeername', `send',
@@ -1201,13 +1202,14 @@ Also, as of the 2.1 release the IPv6 API provided by GNU libc is not
100% complete. In particular the getipnodebyname and getipnodebyaddr
functions are not implemented.
-?? When I set the timezone by setting the TZ environment variable
+??tzdb When I set the timezone by setting the TZ environment variable
to EST5EDT things go wrong since glibc computes the wrong time
from this information.
{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.
@@ -1216,9 +1218,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