At 10:02 AM -0400 7/25/01, Daniel Senie wrote: > Indeed, looking at the code, and at my error logs, it would > appear there's a lack of action other than logging. I get > multiple error messages in the log file for the same error (EPERM > -- Operation not permitted) when a failure occurs. I suspect this > relates to to the TCP session being gone. True, currently Qpopper depends on 'hangup' getting set as a result of a SIGHUP or SIGPIPE. It should set it for an I/O error as well.
- Closing sessions on hangup... Daniel Senie
- Re: Closing sessions on hangup... Randall Gellens
- Re: Closing sessions on hangup... Clifton Royston
- Re: Closing sessions on hangup... Admin Mailing Lists
- RE: Closing sessions on hangup... Peter R. Hubberstey
- Re: Closing sessions on hangup... Daniel Senie
- Re: Closing sessions on hangup... Randall Gellens
- Re: Closing sessions on hangup... Kenneth Porter
- Re: Closing sessions on hangup... Admin Mailing Lists
- Re: Closing sessions on hangup... Daniel Senie
- Re: Closing sessions on hangup... Clifton Royston
