From owner-freebsd-questions Tue Jun 12 5: 5:52 2001 Delivered-To: freebsd-questions@freebsd.org Received: from smtp2.mbox.com.au (smtp2.mbox.com.au [203.103.80.178]) by hub.freebsd.org (Postfix) with ESMTP id B21E537B403 for ; Tue, 12 Jun 2001 05:05:47 -0700 (PDT) (envelope-from bsd-freak@mbox.com.au) Received: from nms2.mbox.com.au (webmail.i7mail.com.au [192.168.20.4]) by smtp2.mbox.com.au (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0GET00B5FG7WUI@smtp2.mbox.com.au> for freebsd-questions@freebsd.org; Tue, 12 Jun 2001 20:04:44 +0800 (WST) Received: from mbox.com.au ([127.0.0.1]) by nms2.mbox.com.au (Netscape Messaging Server 4.15) with ESMTP id GETG7W03.AY8 for ; Tue, 12 Jun 2001 20:04:44 +0800 Date: Tue, 12 Jun 2001 22:04:44 +1000 From: BSD Freak Subject: qpopper anoyances To: freebsd-questions@freebsd.org Message-id: <5c823b5cb8fe.5cb8fe5c823b@mbox.com.au> MIME-version: 1.0 X-Mailer: Netscape Webmail Content-type: text/plain; charset=us-ascii Content-language: en Content-disposition: inline Content-transfer-encoding: 7BIT X-Accept-Language: en Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi everyone, We use qpopper on a pretty busy POP3 / SMTP server and find it almost impossible to do anything from the console or an SSH session (logged in as root) because qpopper continuously outputs the following messages onto the terminal: Jun 12 21:54:02 mail qpopper[39820]: Stats: mb004k 0 0 0 0 203.44.156.149 xxx.xxx.156.149 Jun 12 21:54:57 mail qpopper[39821]: Stats: mb004k 0 0 0 0 203.44.156.149 xxx.xxx.156.149 Jun 12 21:56:51 mail qpopper[39825]: Stats: mb004k 0 0 0 0 203.44.156.149 xxx.xxx.156.149 Jun 12 21:57:10 mail qpopper[39826]: Stats: mb001g 0 0 0 0 203.44.156.154 xxx.xxx.156.154 Jun 12 21:57:45 mail qpopper[39827]: Stats: mb004k 0 0 0 0 203.44.156.149 xxx.xxx.156.149 Jun 12 21:59:13 mail qpopper[39828]: Stats: mb004k 0 0 0 0 203.44.156.149 xxx.xxx.156.149 (I have masked the first part of the IP address) This problem is compounded when logged into the server via a low bandwidth link. I know this has to do with one of the syslog options. Any ideas would be much apreciated. A copy of my /etc/syslog.conf follows: # $FreeBSD: src/etc/syslog.conf,v 1.13 2000/02/08 21:57:28 rwatson Exp $ # # Spaces are NOT valid field separators in this file. # Consult the syslog.conf(5) manpage. *.err;kern.debug;auth.notice;mail.crit /dev/console *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security mail.info /var/log/maillog lpr.info /var/log/lpd-errs cron.* /var/log/cron *.err root *.notice;news.err root *.alert root *.emerg * # uncomment this to enable logging of all log messages to /var/log/all.log #*.* /var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.* @loghost # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !startslip *.* /var/log/slip.log !ppp *.* /var/log/ppp.log ---------------------------------------------- Earn money with mBox Visit http://www.mbox.com.au/referral_programs.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message