01-26-07 12:25 AM
Hi guys,
Thank you very much for all of you.
Because I am going to use this module in a complicated testing
envrionment. There might be unclosed files when the new process is
generated, so I need to solve this problem in the module.
The method I am using now is to go over the file descriptors and close
them. But I got different open_max by using PERL and C. I got 1024 by
using C and 10371 by using PERL on the same system. Does anyone has any
idea?
Thanks again
-Connie
On Jan 25, 5:28 am, Rainer Weikusat <rainer.weiku...@sncag.com> wrote:[vbcol=seagreen]
> j...@toerring.de (Jens Thoms Toerring) writes:
>
>
>
>
>
>
>
>
> internal, there is no reason that the caller, which eventually
> un-FD_CLOEXEC'd something even knew that the descriptor that should
> have been passed to something executed directly on behalf of the
> caller is going to leak through to a second program.
>
> 'having someone to blame' is a sufficient replacement for 'having
> something that works'. This is something I disagree with.
>
> interfaces could possibly relate to 'user-transparent execution of
> programs to accomplish defined tasks'.- Hide quoted text -- Show quoted text -[/vb
col]
[ Post a follow-up to this message ]
|