Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Ulrich Drepper <drepper@xxxxxxxxxx>
- Date: Thu, 31 May 2007 12:50:35 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Davide Libenzi wrote:
What I meant, was that the vast majority of MT+exec
apps wants all their fds (but an handfull, maybe)
You never listen when you are told something. Such a statement cannot
be made. The application doesn't know what the runtime libraries need
(not just libc, libstdc++, libxml, whatever) and vice versa. Policies
are always wrong for somebody and changing the standardized behavior is
not acceptable.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGXycL2ijCOnn/RHQRAvPfAJ9r77oMkReyf4OG2rVPaFNb5TIYfgCgwp8e
mvswKBbe1UlrzlG3oOWYswM=
=viNa
-----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
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Ulrich Drepper
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Davide Libenzi
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Jakub Jelinek
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
- From: Davide Libenzi
- [PATCH] Introduce O_CLOEXEC (take >2)
- Prev by Date: [PATCH] mm: include private data mappings in RLIMIT_DATA limit
- Next by Date: Re: [RFC 2/4] CONFIG_STABLE: Switch off kmalloc(0) tests in slab allocators
- Previous by thread: Re: [PATCH] Introduce O_CLOEXEC (take >2)
- Next by thread: Re: [PATCH] Introduce O_CLOEXEC (take >2)
- Index(es):