At 9:50 AM -0800 11/8/01, Justin Ainsworth wrote: >I was testing out qpopper4.0.4rc1 (I think it came out on the 6th), and >it appears that occasionally it would become non-responsive for me. And >it was intermittent, so one person would connect and one person >wouldn't, than someone else would. > >The platform is Red Hat Linux 6.0, running kernel 2.2.5-22. > >I have reverted back down to qpopper4.0.3, and I am NOT seeing the same >problem.
If possible, could you try and reproduce the situation with 4.0.4fc1 and get a debug trace of it? 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-path>'. 4. Send inetd (or xinetd) a HUP signal. (Steps 3 and 4 are only needed if you use inetd (or xinetd). In standalone mode, you can add '-d' or '-t <tracefile-path>' to the command line directly.) (In either standalone or inetd mode, if you use a configuration file you can add 'set debug' or 'set tracefile = <tracefile>' to either a global or user-specific configuration file instead of steps 3 and 4.) This causes detailed tracing to be written to the syslog or to the file specified as 'tracefile'.
