diff options
author | Rich Felker <dalias@aerifal.cx> | 2012-09-29 17:36:27 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2012-09-29 17:36:27 -0400 |
commit | 79a5e73e518213d5e77a06cfc0db74ffbf7922c6 (patch) | |
tree | a13e64b58de93ae8a94787414007c4db0d72843d /Makefile | |
parent | 3d8d90c5ccf66f1d243cb1b248b047295c197b5c (diff) | |
download | musl-79a5e73e518213d5e77a06cfc0db74ffbf7922c6.tar.gz musl-79a5e73e518213d5e77a06cfc0db74ffbf7922c6.tar.xz musl-79a5e73e518213d5e77a06cfc0db74ffbf7922c6.zip |
emulate SOCK_CLOEXEC and SOCK_NONBLOCK for old (pre-2.6.27) kernels
also update syslog to use SOCK_CLOEXEC rather than separate fcntl step, to make it safe in multithreaded programs that run external programs. emulation is not atomic; it could be made atomic by holding a lock on forking during the operation, but this seems like overkill. my goal is not to achieve perfect behavior on old kernels (which have plenty of other imperfect behavior already) but to avoid catastrophic breakage in (1) syslog, which would give no output on old kernels with the change to use SOCK_CLOEXEC, and (2) programs built on a new kernel where configure scripts detected a working SOCK_CLOEXEC, which later get run on older kernels (they may otherwise fail to work completely).
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions