> Without thinking too hard, I thought that was what the > listener/server-end netcat was supposed to do ... quit when the > connection to it dies ...
One connection or both connections? Because netcat always uses two... It used to terminate when the second (last) connection died/closed/whatever, which was very useful for copying files as it allowed to put the listener on either end. You're supposed to be able to put the listener at either end. Even if you implemented a "web server" with it, the listener mustn't terminate when it's input (the data to serve) has EOF, but when the reader (client) has read the last data and closes the connection. Otherwise you'll never be able to retrieve the last bit of data. Dito for the client - perhaps the client doesn't want to send anything (</dev/null) and only receive - you can't do that currently, as the client buggers off faster than you can look. Either one of us has to think harder... :))) Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
