From: Stephane Chazelas <stephane@chazelas.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Close *all* file descriptors
Date: Mon, 23 May 2022 07:42:22 +0100 [thread overview]
Message-ID: <20220523064222.p6kwduzmsydogf7r@chazelas.org> (raw)
In-Reply-To: <CAH+w=7YZK2WYTEjgAmb-tT8bVKr631wZr=H_Jx+SKUqsQ6CYNg@mail.gmail.com>
2022-05-22 16:23:05 -0700, Bart Schaefer:
[...]
> Or even: ${${(M)$(lsof -p $$ -F F):#f<->*}#f}
>
> Curiously, despite the man page for lsof asserting that PID filters
> are applied first, if you add a -d filter to include only certain
> types of descriptors, you get the descriptors for every process.
[...]
You also need -a for "and" (default being "or"):
lsof -w -Ff -p $$ -a -d 3-999999 | sed -n 's/^f//p'
(-F F would be "F file structure address (0x<hexadecimal>)"
according to the manual, I need -F f for fds here).
Here, doing:
sh -c 'exec lsof -w -p "$$" -Ff -ad3-999999' | sed -n 's/^f//p'
Would filter out the fds that have the close-on-exec flag (as
I'd expect would be the case for the internal fds of zsh which
we don't want to close).
(would also filter out the ones created by the user with
sysopen -o cloexec and might list internal sh fds).
--
Stephane
next prev parent reply other threads:[~2022-05-23 6:43 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
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 [this message]
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=20220523064222.p6kwduzmsydogf7r@chazelas.org \
--to=stephane@chazelas.org \
--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).