From: Tristan Wibberley <tristan.wibberley@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: New system call wanted: fdreopen
Date: Sun, 9 Dec 2012 17:18:23 +0000 (UTC) [thread overview]
Message-ID: <ka2h4v$ra3$2@ger.gmane.org> (raw)
In-Reply-To: 20121209162746.GA23890@thunk.org
On Sun, 09 Dec 2012 11:27:46 -0500, Theodore Ts'o wrote:
> On Sun, Dec 09, 2012 at 03:03:30PM +0000, Tristan Wibberley wrote:
>>
>> - /proc/self/fd/* does not solve this problem because the file might no
...
> Actually, /proc/self/fd/* _will_ work. When you do a ls -l, it looks
> like a symlink, but the files in /proc/self/fd (and /proc/<pid>/fd more
> generally) are magic. If you open files in /proc/<pid>/fd/*, it will do
> what you want.
Oh! Cool! By reading how to solve this class of problem with google
search results I couldn't find any indication that /proc/pid/fd/* worked
differently than a symlink.
Thanks for your quick reply.
--
Tristan
next prev parent reply other threads:[~2012-12-09 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 15:03 New system call wanted: fdreopen Tristan Wibberley
2012-12-09 16:27 ` Theodore Ts'o
2012-12-09 17:18 ` Tristan Wibberley [this message]
2012-12-09 19:37 ` Chris Adams
2012-12-09 20:47 ` Al Viro
2012-12-10 10:18 ` Kevin Easton
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='ka2h4v$ra3$2@ger.gmane.org' \
--to=tristan.wibberley@gmail.com \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox