Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Ulrich Drepper <drepper@xxxxxxxxxx>
- Date: Thu, 31 May 2007 11:42:19 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Davide Libenzi wrote:
Isn't this better be a global process flag? Default should be, for legacy
reasons,
No. Policies are always wrong since it means code that cannot change
the policy (e.g, all runtime libraries) have no access to the
functionality. I cannot set the policy to default to close-on-exit in
glibc all the while the application assumes this is not the case.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGXxcK2ijCOnn/RHQRAmM9AKC5BEIEBsgwhWx09aAMA0CwsesMWQCfScGr
vCF+Ih1lDP5rliY8D2Om5vU=
=ZShC
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Davide Libenzi
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
- References:
- [PATCH] Introduce O_CLOEXEC (take >2)
- From: Ulrich Drepper
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Davide Libenzi
- [PATCH] Introduce O_CLOEXEC (take >2)
- Prev by Date: Re: 2.6.22-rc3-mm1
- Next by Date: Re: [PATCH 13/22] 2.6.22-rc3 perfmon2 : common core functions
- Previous by thread: Re: [PATCH] Introduce O_CLOEXEC (take >2)
- Next by thread: Re: [PATCH] Introduce O_CLOEXEC (take >2)
- Index(es):
Relevant Pages
|
