If LyX is following me and thinking that LyX should be using anonymous pipes (multiple, at least one for input and one for ouput) or a pair of connected sockets crreated by socketpair(2) for remote connections then it is much simpler.
Neither pairs of pipes or pairs of connected sockets of never involves anything with a name and no connectioon is required: a process is connected by virtue of the fiel descriptors it inherets from the child the lyx server uses to invoke it. If nobody is at home at the other end of a connection writing to it raises SIGPIPE or returns -1 and set errno to EPIPE (if SIGPIPE is caught, blocked or ignored according the manpage). You might also notice that the reading end of a process attatched this way is readable and read(2) returns 0, i.e. end of file. And given the lyxserver can know the pid it could notice that the process terminating by catching SIGCHLD. At least some of these mechamism work on windows as well. -- Duncan (-: "software industry, the: unique industry where selling substandard goods is legal and you can charge extra for fixing the problems."
