At 3:21 PM -0700 9/24/08, Kelson wrote:
Lately I've been seeing popper processes sticking around on our
server for days. Always the same few users, often several
processes per user. Their .pop files have already been deleted, so
they aren't preventing new connections, but they have been
cluttering things up.
I tracked them to iPhone users. It doesn't happen on every POP,
maybe once every day or two.
We're using popper via xinetd so that we can run both STARTTLS and
the alternate-port SSL connection. At first I thought it was
specific to the alternate-port SSL, since those were the only ones
that showed up, but after asking one user to switch to STARTTLS,
it's still happening.
Qpopper 4.0.14 on x86 Linux. server-mode and fast-update enabled.
I'm reluctant to install the 4.1 beta, since it's working
otherwise, but I'll consider it if there's a relevant fix.
Has anyone else seen this sort of thing? Any suggestions?
I'd be interested to know what state these processes are in, and what
they did up to the point where they hang.
How heavy is the activity from any of the affected users? If it's
feasible, I'd really like to see Qpopper tracing and kernel tracing
(e.g., ktrace) of an affected session. You can use a per-user
configuration file to enable tracing for just one user, for example.
Kernal tracing is harder to do per-user, unless you can get a user to
switch to a different port.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
The forceps of our mind are clumsy things and crush the truth a little
in the course of taking hold of it.
--H.G. Wells
