in reply to IO::Socket::UNIX recvmsg error

I think you want a named pipe (see man mknod), not a UNIX domain socket. It still may have problems (for example, your writer may try and seek on the descriptor), but I think you're barking up the wrong tree with a UNIX domain socket.

Replies are listed 'Best First'.
Re^2: IO::Socket::UNIX recvmsg error
by fuzzyping (Chaplain) on May 16, 2005 at 02:21 UTC
    Yes, the writer does indeed try to seek on the descriptor. I gave up trying to use fifo/pipes for just this reason.

    -fp
      In this case, FIFOs would actually be more appropriate than sockets. Sockets are analogous to TCP or UDP connections (which is no coincidence), whereas FIFOs are closer to "ordinary" file operations. But since you've already been down that road, you'll have to look elsewhere.

      Have you considered processing lines from the file as they arrive, tail -f style?
        Tailing it won't work either. I'm using djm's Flowd, which expects you to init() the logfile. It does not accept stdin as a interface for conversion. I'm working with djm right now, it appears the fifo problem is a bug with flowd.

        Thanks,

        -fp