From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
Description of problem:
after installing imap-2000c-1.6.0 and related packages I discovered pop3
v2000.70rh crashes when it reaches it's default inetd.conf limit
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.connect to port 110 41 times very quickly
Actual Results: pop3 falls over and needs a restart
Expected Results: should not spawn another pop as its maxed out.
quick kludge fix alter this line in /etc/inetd.conf
pop-3 stream tcp nowait root /usr/sbin/tcpd ipop3d
pop-3 stream tcp nowait.1024 root /usr/sbin/tcpd ipop3d
That would IMHO be an inetd problem, as inetd spawns imap.
My server is using inetd-0.16-7, I think this is the latest version from RH?
RHL 6.2 uses inetd, not xinetd - assigning back.
Pong. I don't own inetd anymore, no matter what bugzilla thinks.
Please find some other means to resolve this problem.
You can reassign owner without changing to the wrong component.
That presumes that I know who the appropriate owner
is, a context which I do not have.
Instead I've chosen to assign to the owner of the closest related
package in the hopes that their context and knowledge is superior
to my own.
pts/5 mharris@porkchop:~$ who-owns inetd
Probably this should be brought up on an internal mailing list for
discussion then. Someone should look into it, and inetd should be
assigned to someone. It isn't a good idea for any package to be
If imap/pop crashes, it would be an imap issue. If it is just the system being
overloaded by many connects, it would be a local configuration issue (add the
maxconnect specifier suggested by the reporter). Mike, does imap/pop really crash?
Closing due to lack of feedback.