xinetd[31993]: FAIL: imaps service_limit from=68.27.134.242
xinetd[31993]: FAIL: imaps service_limit from=68.27.134.242
xinetd[31993]: FAIL: imaps service_limit from=68.27.134.242
xinetd[31993]: FAIL: imaps service_limit from=68.27.134.242
xinetd[31993]: FAIL: imaps service_limit from=66.134.33.83
xinetd[31993]: FAIL: imaps service_limit from=66.134.33.83
....
Was looking in /var/log/messages and /var/log/maillog, but this was being logged to /var/log/security.
:)
Mark Crispin wrote:
On Tue, 18 Feb 2003, Justin Georgeson wrote:Someone suggested UW imap is coded to "take a break" if things get a little too heavy, and mentioned a parameter like "wait:200" in /etc/inetd.conf. I run with xinetd, and have "wait = no" for both imap and imaps, and so no warning in /var/log/maillog that imapd was about to lay low.There is nothing like that in imapd; but both inetd and xinetd have features to shut down over-used services. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate.
-- ; Justin Georgeson ; http://www.lopht.net ; mailto:[EMAIL PROTECTED] ; "Free the mallocs, delete the news"
