Pete's Log: robust sockets code

Entry #577, Fri, November 10, 2000, 15:48 EST (Coding, Hacking, & CS stuff)
(posted when I was 22 years old.)
hrmm... I'm beginning to get the feeling that writing robust sockets code isn't really possible. My new problem is that, having installed signal handlers, accept is segfaulting (and this time it's not even in my code) when my program catches a signal. hrmmm... so I think I'm gonna say screw the signal handling, fix up the rest of the code, and go running. I have managed to restore the code to a functional state (excluding, of course, the signal handling) so I can at least turn it in and get full credit (in theory), even if I've not accomplished my personal goals for the project. That's ok, the code does work on heterogeneous networks, so I feel like a badass already. Hopefully I won't break anything as I attempt to ungraft all this ugly signal handling stuff from my code. Although thinking about it, maybe I should play with this some on solaris, I wonder if the accept segfault is a linux thing...

woah! It is freaking linux. It fucking works on solaris! Damn. Stupid linux. So here's the tradeoffs: linux gives you 8 times as many file descriptors as solaris, solaris works right. heh. man I feel a lot better now. Except I'm slightly angry that linux has proven to suck.
Nobody has rated this entry.