[PATCH] Avoid having a dead Plymouth cause clients to get SIGPIPE'd

[Ray Strode]

Hey,

On Mon, Feb 21, 2011 at 7:14 AM, Soren Hansen <soren at linux2go.dk> wrote:
> If Plymouth dies for some reason, clients will get SIGPIPE'd next time
> they try to talk to it. Address this by passing MSG_NOSIGNAL to send
> and leave it to standard errno handling to deal with the error.
>
> Since ply_write is used for non-socket communication as well, first
> attempt to use send(2), then fall back to write(2).
Any reason your client doesn't signal (SIGPIPE, SIG_IGN) ?  Almost
every program should be doing this (with possibly the exception of
some small, special purpose apps designed to run in pipelines like say
cat)

--Ray