zsh-users
 help / color / mirror / code / Atom feed
From: Zach Riggle <zachriggle@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Close *all* file descriptors
Date: Sun, 22 May 2022 05:49:50 -0500	[thread overview]
Message-ID: <CAMP9c5kJ-zf1-Kyj0Px6dcXA9usPx_jcHN+M=0Y_uPfMNnC=sQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZD9eHt-+AdVanOJru7r0JqDnT+FYqE5LRor2wt_bS8Bw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]

Unfortunately, macOS does not support proofs, so there’s no nice way to do
it the way you recommended.

I can just force-close the first 1024 file descriptors that I don’t care
about, and hope that it’s sufficient.

On Sat, May 21, 2022 at 3:02 PM Bart Schaefer <schaefer@brasslantern.com>
wrote:

> On Fri, May 20, 2022 at 11:32 PM Zach Riggle <zachriggle@gmail.com> wrote:
> >
> > This is probably an usual request, but is there any way to close (or
> redirect to /dev/null) all open file descriptors known / opened by zsh?
>
> I expected this to work if you have /proc/:
>
> opened=(/proc/self/fd/*(:t)) wanted=(0 1 2 10)
> for close in ${^${opened:|wanted}}; exec {close}>&-
>
> But zsh temporarily opens a file descriptor (for xtrace output, I
> believe) during the assignment to $opened, and it's not possible to
> predict what number that descriptor will have, which means one of
> those exec is going to error on bad file descriptor and kill the loop.
>
> So ... the following seems to be pretty good, though on repeated tries
> I have sometimes seen descriptors remain open:
>
> integer close
> for close in /proc/self/fd/*(:t); [[ -h /proc/self/fd/$close && ! -t
> $close ]] && exec {close}>&-
>
> > Is there a way to close all of them in a concise way that does not
> affect e.g. shell pipelines and redirection (i.e., stdout and stderr)?
>
> No guarantees about that.  If there are descriptors open for temporary
> files, etc., that are needed by coproc or whatever, this could break
> it.
>
-- 

*Zach Riggle*

[-- Attachment #2: Type: text/html, Size: 2263 bytes --]

  reply	other threads:[~2022-05-22 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  6:29 Zach Riggle
2022-05-21 20:02 ` Bart Schaefer
2022-05-22 10:49   ` Zach Riggle [this message]
2022-05-22 19:17     ` Dominik Vogt
2022-05-22 19:49       ` Dominik Vogt
2022-05-22 23:23         ` Bart Schaefer
2022-05-23  6:42           ` Stephane Chazelas
2022-05-23  8:56             ` Dominik Vogt
2022-05-23  0:28       ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMP9c5kJ-zf1-Kyj0Px6dcXA9usPx_jcHN+M=0Y_uPfMNnC=sQ@mail.gmail.com' \
    --to=zachriggle@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).