OpenE2K
/
glibc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update. 

1999-01-20  Ulrich Drepper  <drepper@cygnus.com>

	* sysdeps/unix/sysv/linux/vfork.c: Once again use generic version.
This commit is contained in:
Ulrich Drepper 1999-01-20 11:36:34 +00:00
parent 5d003fb2ea
commit 8b4a471567
4 changed files with 20 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,3 +1,7 @@
1999-01-20 Ulrich Drepper <drepper@cygnus.com>
* sysdeps/unix/sysv/linux/vfork.c: Once again use generic version.
1999-01-18 Andreas Schwab <schwab@issan.cs.uni-dortmund.de>
* sysdeps/unix/sysv/linux/Makefile ($(objpfx)syscall-%.d): Fix

12
FAQ
View File

@ -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

14
FAQ.in
View File

@ -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

1
sysdeps/unix/sysv/linux/vfork.c Normal file
View File

@ -0,0 +1 @@
#include <sysdeps/generic/vfork.c>