From: "David S. Miller" <davem@redhat.com>
To: spotter@cs.columbia.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: file descriptor passing (jail related question)
Date: Fri, 19 Jul 2002 14:53:24 -0700 (PDT) [thread overview]
Message-ID: <20020719.145324.122050429.davem@redhat.com> (raw)
In-Reply-To: <1027115899.2161.110.camel@zaphod>
From: Shaya Potter <spotter@cs.columbia.edu>
Date: 19 Jul 2002 17:58:07 -0400
How does file descriptor passing work. From what I can tell it uses the
sendmsg and recvmsg calls. Is this only process to process over a non
ip socket on the same machine (what's the right terminology for this,
just a plain FIFO?), or could one conceivably pass a file descriptor
over an ip socket?
File descriptors can only be passed over AF_UNIX sockets.
These are like fancy FIFO's on the local host using the
socket APIs for the communication and synchronization.
next prev parent reply other threads:[~2002-07-19 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 21:58 file descriptor passing (jail related question) Shaya Potter
2002-07-19 21:53 ` David S. Miller [this message]
2002-07-19 22:35 ` Shaya Potter
2002-07-29 11:37 ` Bill Davidsen
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=20020719.145324.122050429.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.