Mick wrote: >> File "/usr/lib64/python2.7/SocketServer.py", line 694, in finish >> self.wfile.flush() >> File "/usr/lib64/python2.7/socket.py", line 303, in flush >> self._sock.sendall(view[write_offset:write_offset+buffer_size]) >> error: [Errno 32] Broken pipe >> ---------------------------------------- >> > I'm pretty much clueless in python so can't interpret the messages - > hopefully someone more knowledgeable will chime in. > 'Broken pipe' just means the remote closed the connection. It's a pretty standard error in this context, which the server should handle.
A process normally gets a SIGPIPE which will by default terminate it, which is what you want if you have a pipeline'd command whose output is no longer required. An example would be checking there is at least one matching file somewhere in a directory hierarchy with: read -d '' f < <(find /base/dir -type f -name 'foo*' -print0) [[ $f ]] || echo 'no foo* files' -- find will terminate after the first filename has been read. In this case, signal(SIGPIPE, SIG_IGN) or the equivalent has been called, which gives EPIPE instead; a process ignoring the signal is supposed to deal with the error. So I'd say it's a bug. -- #friendly-coders -- We're friendly, but we're not /that/ friendly ;-)
