popa3d-users - Re: logging problems...

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / news community lists wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Sun, 30 Jun 2002 22:47:24 +0400
From: Solar Designer <solar@...nwall.com>
To: popa3d-users@...ts.openwall.com
Subject: 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?

> 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