Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EIEAIODGBKOFFGDNBPFEMEGNCBAA.andis@bossmail.de>
Date: Sun, 30 Jun 2002 21:07:07 +0200
From: "Andi" <andis@...smail.de>
To: <popa3d-users@...ts.openwall.com>
Subject: AW: logging problems...



-----Ursprungliche Nachricht-----
Von: Solar Designer [mailto:solar@...nwall.com]
Gesendet: Sonntag, 30. Juni 2002 20:47
An: popa3d-users@...ts.openwall.com
Betreff: Re: logging problems...


On Sun, Jun 30, 2002 at 08:29:00PM +0200, Andi wrote:

Hi,

> i'm using slackware 8.1 with popa3d.

Are you using the popa3d package included with Slackware or did you
build popa3d yourself?





--> yes i?m using the included package in slackware. i didn?t compiled it
myself.
	i?m a linux newbee...can you explain exactly what to do?
	i?ve to remove the old package and compile the new one by myself with which
options?

thanks andi






> i want to stop popa3d logging in /var/log/messages when a client contacts
> his mailbox!
> is this possible? and how can i do it?

Well, currently the log facility and priority popa3d uses are defined
at compile time in params.h.  If you're using the distribution-provided
package you need to either get the distribution to apply the change or
switch to building popa3d from source yourself.

Where messages for a given facility/priority are routed is of course
specified in /etc/syslog.conf.

On some systems, the logging daemon (syslogd or equivalent) is able to
route messages based on the ident ("popa3d" in this case).  There you
wouldn't have to apply any configuration changes to popa3d itself.

--
/sd

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.