[ Date Index ][
Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Named pipes are part of the file system, so that rules out networking really, unless you use NFS (Warning: kludge alert). Now AFAIK the main uses of named pipes are for simple interprocess communications, without the overhead of AF_UNIX sockets (or even AF_INET). For example /dev/log is a named pipe I think, used for communication with syslogd locally. These days people do tend to just use AF_INET sockets and connect to loopback. J. On Tue, 2 Jul 2002, Adrian Midgley wrote:
I've been looking at named pipes. Is the sort of thing I might do with a named pipe on the network to have a program reading from it, and several programs intermittently opening it to write into, as a way of avoiding concurrent updates to a single log file? Or is that much better done in other ways, in whcih case what is the point of them?
-- Jon Still E-mail: jon@xxxxxxxxxxx tertial.org Web: http://www.tertial.org/ GPG Key: http://xanthein.net/key.asc Key ID: 0x00493D2B -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.