Sig PIPE: The signal of Doom. DHOOOOOOOM!

*#$”!:3-@#*#!%(#)*$&(@*!^%

Not that I’m a big fan of Unix signal‘s at the best of times, they’re least problematic in a single-threaded, single-purpose application where you can have a fairly good expectation of what’s going on when a signal is raised.

But SIGPIPE is a real pain in the backside. You can get it from all kinds of things: database connections, log files, network connections, etc, etc.

For some reason, one of our installations has started getting SIGPIPEs all over the place, and I’m having to go through the code and find all the sigpipe leaks (we generally ignore it because there is just too much going on to be able to efficiently interact with sig pipe – we’re perfectly happy waiting for an EPIPE return code from whatever function is trying to send data, thanks).

 

Leave a Reply

Name and email address are required. Your email address will not be published.

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

You may use these HTML tags and attributes:

<a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <pre> <q cite=""> <s> <strike> <strong> 

%d bloggers like this: