From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: Unix Domain Sockets
Date: Mon, 24 Jan 2005 20:32:00 +0100 [thread overview]
Message-ID: <20050124193200.GD28037@lug-owl.de> (raw)
In-Reply-To: <20050124_191803_058538.r_zaca@ig.com.br>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On Mon, 2005-01-24 17:18:03 -0200, r_zaca <r_zaca@ig.com.br>
wrote in message <20050124_191803_058538.r_zaca@ig.com.br>:
Content-Description: Mail message body
> Hello everybody,
>
> Does anyone know what a "unix domain socket" is, and how it differ from an
> "Internet domain socket"?
Internet domain sockets work with IP addresses and port numbers. A unix
socket merely is a special file on a local file system, a so calles
"fifo". It's created with the "mkfifo" library call or userspace
command.
After you've created a fifo, which is displayed with a 'p' as the
file-type at "ls -l" output, you can open/close/read/write it.
> If you know a nice site or documentation about this subject, please tell
> me.
There's not much to tell about it. It's created once locally, then you
can access it. Keep in mind that it's a purely local thing. You cannot
export it by any means (I've seen people putting it on a shared NFS
filesystem....). The data passed through the fifo is kept within the
operating system's kernel; it's never ever written somewhere onto stable
storage.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-24 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 19:18 Unix Domain Sockets r_zaca
2005-01-24 19:32 ` Jan-Benedict Glaw [this message]
2005-01-30 11:35 ` Glynn Clements
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=20050124193200.GD28037@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@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 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.