One more attempt: stuck processes

[Ken Murchison]

Sebastian Hagedorn wrote:
> -- Ken Murchison <murch at andrew.cmu.edu> is rumored to have mumbled on 
> 19. November 2007 12:35:46 -0500 regarding Re: One more attempt: stuck 
> processes:
> 
>> How are things looking today?
> 
> Good! When I just checked I thought I'd found a new hanging pop3d 
> process, because it's been around for 6 hours, but in fact it's still 
> working:
> 
> Nov 19 14:17:16 lvr13 pop3s[23493]: badlogin: p50865731.dip.t-dialin.net 
> [80.134.87.49] LOGIN user not found
> ...
> Nov 19 19:04:23 lvr13 pop3s[23493]: badlogin: p50865731.dip.t-dialin.net 
> [80.134.87.49] LOGIN user not found
> Nov 19 19:04:27 lvr13 pop3s[23493]: badlogin: p50865731.dip.t-dialin.net 
> [80.134.87.49] LOGIN user not found
> Nov 19 19:04:30 lvr13 pop3s[23493]: badlogin: p50865731.dip.t-dialin.net 
> [80.134.87.49] LOGIN user not found
> 
> Sigh. But that's beside the matter. The only other potential downside 
> the patch has is that stracing or gdb'ing it causes the timeout to 
> trigger prematurely. AFAIK that's a common issue for signals. I'm not 
> sure if there's something that could be done about that, i.e. catching 
> ERESTART or something like that?

Is this only a problem with pop3s, or does it also effect the STLS command?

-- 
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University