Brian,
I am running qpopper 4.0.5 on several Sparc Solaris 9 and 10 systems. I am not
currently seeing this issue. This is what I have used for my compile time options:
./configure --disable-apop \
--enable-specialauth \
--enable-uw-kludge \
--disable-check-pwmax \
--enable-log-login \
--without-pam \
--enable-temp-drop-dir=/var/tmp
I don't know if this will help you or not, but it will give you something to
compare with.
Jerry K
Brian Parent wrote:
We're seeing some qpopper processes hanging around for months.
They're on Solaris 8 and 10 boxes.
truss shows they're waiting on a read of descriptor zero.
lsof shows descriptor zero is a tcp connection to a remote
system, which is usually not currently on the network.
I've verified that the kernel parameter tcp_keepalive_interval
is set to two hours, but apparently, the qpopper code isn't
using the SO_KEEPALIVE socket option.
A search through the source (qpopper4.0.5), doesn't turn up
any such strings.
A search of archives for this mailling list ([email protected])
turned up some mention of similar issues, and mention of keepalives,
so I expect to find it in the source, but no luck.
The official FAQ
http://www.eudora.com/products/unsupported/qpopper/faq.html
wasn't fruitful either.
Any help appreciated.
