Re: fork/exec & close file descriptors

References	<CANc-5UyeaWqThGFSAuGskz+S2Lrgq0ia9W9DHAie28t9GY+sww@mail.gmail.com> <CAPTjJmoj4STV9+t2-9JWed3t6Hxk5ibtaxYSFfX31oGz=kKR1g@mail.gmail.com> <CANc-5UwUxYjg=rQQ0Z_nM3s7o4+ghVYzG-9ajQY=LERWAsPrKw@mail.gmail.com> <CAPTjJmrdPcW8EkLR9Kq+n9sYEWB8eJ3fg=_JFQ2x_4QhDeg90Q@mail.gmail.com> <CANc-5UwWcJm_S7QMtP2gC1aW5U=iQRvrxVb=dPWjzE78-rL_9w@mail.gmail.com>
Date	2015-05-20 01:13 +1000
Subject	Re: fork/exec & close file descriptors
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.140.1432048432.17265.python-list@python.org> (permalink)

Show all headers | View raw

On Wed, May 20, 2015 at 12:31 AM, Skip Montanaro
<skip.montanaro@gmail.com> wrote:
> On Tue, May 19, 2015 at 8:54 AM, Chris Angelico <rosuav@gmail.com> wrote:
>>
>> On Linux (and possibly some other Unixes), /proc/self/fd may be of
>> use.
>
>
> Good point. Yes, /proc/PID/fd appears to contain all the entries for open
> file descriptors (I am on Linux).

Yes, and /proc/self is usually a magic symlink to /proc/<your_pid> so
you can just look at /proc/self/fd instead of explicitly calling up
your own PID.

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: fork/exec & close file descriptors Chris Angelico <rosuav@gmail.com> - 2015-05-20 01:13 +1000

csiph-web