Re: gnutv should not ignore SIGPIPE

2011-11-29 Thread Brian J. Murrell
On 11-11-25 08:36 AM, Brian J. Murrell wrote: Yes, that is the other way to skin that cat I suppose. I couldn't figure out what the right thing for writer thread to do to terminate the application so I used SIGPIPE instead. Here's the patch: ---

gnutv should not ignore SIGPIPE

2011-11-25 Thread Brian J. Murrell
Currently, (at least in rev. 1355) gnutv is ignoring SIGPIPE: signal(SIGPIPE, SIG_IGN); This means though that if it is used as such: gnutv -out stdout -channels /home/mythtv/channels.conf.found 91-472 | mplayer - It will not terminate as it should when/if it's consumer (mplayer in the

Re: gnutv should not ignore SIGPIPE

2011-11-25 Thread Rémi Denis-Courmont
Le vendredi 25 novembre 2011 15:05:44 Brian J. Murrell, vous avez écrit : Is there a good reason I am not seeing why gnutv should be ignoring SIGPIPE? In general, ignoring SIGPIPE is the easiest way to protect against denial of service when a peer connection socket is hung up remotely.

Re: gnutv should not ignore SIGPIPE

2011-11-25 Thread Brian J. Murrell
On 11-11-25 08:34 AM, Rémi Denis-Courmont wrote: Anyway, the problem is not so mucgh ignoring SIGPIPE as ignoring EPIPE write errors. Yes, that is the other way to skin that cat I suppose. What's the best/proper way to go about getting this fixed? Cheers, b. signature.asc Description: