egghelp.org community

[Ofloo]

How do I create a named pipe instead of creating a socket to listen on. I've been searching google, looking through the manual, but I can't find anything about named pipes.
_________________
XplaiN but think of me as stupid

[rosc2112]

Read about pipelines in the manpage for open:
http://www.tcl.tk/man/tcl8.4/TclCmd/open.htm

[Ofloo]

As far as I know is what you're suggesting only for execution.

[nml375]

Been a while since I played around with named pipes, but as I recall you create them with 'mknod' or 'mkfifo' and then just use them as regular files:

Example using two concurrent shell-sessions:
Session 1

[Ofloo]

i was thinking of making a script listen on a unix socket.
like:

[nml375]

As far as I know, there is no support for unix sockets in tcl.
Also, keep in mind that "named pipes" is something completely different from "unix sockets", where the first one uses simple file I/O for communications while the second makes use of the kernels support for socket communication, with the domain AF_UNIX rather than AF_INET (which is used for IP sockets).

I suppose IP sockets won't cut it for you?

If you really want unix sockets, you'd have to create some wrapping-code to provide the function calls from the socket-library to the tcl-environment (possibly by creating an eggdrop module).
One option, I guess, would be to write your project entirely as a module rather than a tcl-script.
_________________
NML_375, idling at #eggdrop@IrcNET

[Sir_Fz]

Perhaps user's code would help: socket api - nonblocking tcp made easy.
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[Ofloo]

I know how to use sockets, it's just that i want a to create a unix socket.

ok it's

[nml375]

Keep in mind that named pipes are "one-way connections", that is, one client must open the fifo in readonly mode, and other client in writeonly mode.

Btw, if you wanted to work with unix socket, why were you asking for named pipes?
_________________
NML_375, idling at #eggdrop@IrcNET

[Ofloo]

I asked for a named pipe which functioned as a socket, UNIX sockets I suppose.

i want to be able to '|' pipe data from syslogd to a script.

but since reading from stdin is having some issues.. i wanted to use pipes instead.
_________________
XplaiN but think of me as stupid

[nml375]

Pipes and sockets (IP/IPX/Unix/etc all alike) are two completely different concepts, hence there is no "named pipe with socket functions" (unix or otherwize).
Pipes are used just like any other file-stream, whereas sockets have a far more complex structure.

As for your intent to send data from syslogd; a quick check in the manual page would reveal that syslogd allows files, ip/udp, and named pipes to be destination for logmessages. It does not, however, support unix sockets as destination.
_________________
NML_375, idling at #eggdrop@IrcNET