[SM-imapproxy] nasty bug?

[<noe...@au...>]

Hey all,

We had a webmail machine vent a few caps overnight (of course overnight 
- nothing ever falls over in business hours *sigh*) we were on it fast, 
ripped the drives out and into standby hardware, detected  and boted, 
but we forgot that udev is as nasty as systemd in taking control of your 
system, and decided to reassign eth0 to eth1, so no interfaces were seen 
to be present and consequently none was upped, of course causing all 
sorts of nastyness for dovecot and apache, but they aborted their 
startup after a few seconds, however imapproxy was another case, it 
hung.....and hung.... and hung....

Why is there no load abort timeout?

Might I suggest this is bug, and one that requires attention sooner, 
rather than later, so those dragged in at 1am dont have to think of 
everything :)