segfault with unresponsive/timeout socket about slurm-drmaa

[natefoo]

This may also have been fixed by a6f3391. If not, it'd be helpful to know specific cases where this occurs. Each place in the code where it can occur has to handle the error condition separately.

[unode]

This one is hard to reproduce... So far I've only seen it when the submission node or the network is overloaded. Reproducing it might mean a couple of angry emails from local IT 😄.

Feel free to close. I'll re-open if I see it again.
Thanks for all the fixes.

[natefoo]

I don't doubt that there are cases where this occurs, thanks for reporting. If I get a chance I'll audit all the slurm calls to make sure they're all error-handled.