>From my own experiences, the error is very likely the result
of the pop client not waiting for qpopper to disconnect first.
Since this is out of our control and appears with about
half of our user base (we get 5-10 pops per second), I just
commented the error out and recompiled. Blessed silence ;)
On Fri, Apr 13, 2001 at 12:22:23PM -0700, Randall Gellens wrote:
> At 3:03 PM -0400 4/13/01, Lisa Casey wrote:
>
> > After upgrading, I am now seeing this message in /var/log/messages. What
> > does this error mean? I have not encountered this one before.
> >
> > Apr 13 14:41:35 i2000 -sR[21771]: I/O error flushing output to client hkj at
> > 205
> > .160.50.55 [205.160.50.55]: Operation not permitted (1)
>
> My guess is that the client disconnected, or some other error
> occurred earlier. The log should have that error as well.
>
> If these errors persist, try enabling debug tracing.
>
> To enable tracing in Qpopper:
>
> 1. Do a 'make clean'
> 2. Re-run ./configure, adding '--enable-debugging'.
> 3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
> 4. Send inetd a HUP signal.
>
> This causes detailed tracing to be written to the syslog (if you
> used '-d') or to the file specified as 'tracefile'.
--
Michael Smith ... We build e-business infrastructure solutions
SysAdmin, DataFoundry.net ... www.datafoundry.net
