Rbarnes - One thing to note. I had symptoms of connections not closing like you describe some time ago. The problem was due to a configuration error in the qpopper.config file. The reason I mention this is that I beat my head looking for a problem with qpopper that was due to my error in the config file. I am not saying the syntax that you are using through inetd.conf is incorrect, or that your config file is wrong. But I do suggest double checking your configuration, because I experienced the exact same problem. Once I set the config file straight, Qpopper worked much better. There are some messages in the archive on this list to this effect.
Regarding the other Solaris 8 specific problems people are reporting. This is Interesting. We have been experiencing reasonably good Qpopper performance ( 3.0.2 ) on Solaris 8 since our upgrade from 2.6 in January. However, we are seeing substantial slowness for our IMAP users. ( We use UW-IMAP -- can't wait for that patch providing compatible locking, Clifton. I clean up lots of invalid mailbox headers. ) The CPU idle time is 0% most of the day. Our disks are always very busy, but don't seem to be the bottle neck. I am very interested in learning about Sun's response. We have a trouble ticket open with them too. We have applied patches, and rebooted the server the last two weekends in an attempt to eliminate the problem. But this has not been effective yet. We have a user base of about 15,000 users. I hope that some more light is shed on this issue in the near future. Christopher Crowley TIS Network Services Tulane University [EMAIL PROTECTED] 504.314.2535 PGP Key ID: 0x7CF18FDB ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "ListServ" <[EMAIL PROTECTED]> Cc: "Subscribers of Qpopper" <[EMAIL PROTECTED]> Sent: Friday, March 15, 2002 3:16 PM Subject: Re: Problems with Solaris 8 and Qpopper - multiple versions > > > >I work for an ISP, and we have several thousand email accounts. My > >currently POP server is running Solaris 2.5.1 and Qpopper 3.1.2. Other than > >the fact that the box is getting older, and drive space is becoming limited, > >the box is running fine. > > > >I'm attempting to upgrade my POP server to a new box (bigger) running > >Solaris 8. I've configured the box, and thought everything was working > >great. I put the new box in service yesterday morning, and at first > >everything was humming along great -- this was in the early morning hours, > >when utilization was low. As it got closer to peak time (8am) things > >started to worsen and worsen quickly. > > We also have this problem, and it is clearly a Solaris 8 problem, as we > have two identical machines, one Solaris 2.6, one Solaris 8, both > running the same version of Qpopper, and both with the same load, as we > use DNS and round-robin to share the load. We run a simple Perl program > to simulate a POP session and time the response, and the response for > the Solaris 8 system under load is sometimes much worse, by an order of > magnitude, than the Solaris 2.6 system. We currently have an open call > with Sun about this, but they want us to apply the latest patches first, > which we hope to do next week. Do you use NFS ? We have a single mail spool > which is NFS mounted, and wonder if there is a concurrency problem with > NFS or file locking. > > > > Adrian Barker, Information Systems > University College London, Gower Street, London WC1E 6BT > External phone: (+44) 020 7679 2795, Fax (+44) 20 7388 5406 > Internal phone: x 32795 > Email: [EMAIL PROTECTED] >
