Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 3 Jul 2002 18:17:21 +0400
From: Solar Designer <solar@...nwall.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: logging problems...

On Wed, Jul 03, 2002 at 11:41:29AM +0200, Andi wrote:
> this is not too complicated for me...(i hope so...)
> i put the LOG_LOCAL0 in this section:
> 
> #define SYSLOG_IDENT                    "popa3d"
> #define SYSLOG_OPTIONS                  LOG_PID
> #define SYSLOG_FACILITY                 LOG_DAEMON
> #define SYSLOG_PRIORITY                 LOG_NOTICE
> #define LOG_LOCAL0

This is wrong.  You were supposed to change the #define SYSLOG_FACILITY
to use LOG_LOCAL0 instead of LOG_DAEMON.

> params.h:162: warning: `LOG_LOCAL0' redefined

This is because of you doing the wrong thing as I've just explained.

> auth_shadow.o: In function `auth_userpass':
> auth_shadow.o(.text+0xbd): undefined reference to `crypt'
> auth_shadow.o(.text+0xd2): undefined reference to `crypt'

And this is because you need -lcrypt as Michael Meyer has correctly
pointed out (and as explained in INSTALL which you should have read).

> i?m using the popa3d-0.5.tar.gz

Why not 0.5.1?

> -----Ursprungliche Nachricht-----
> Von: Solar Designer [mailto:solar@...nwall.com]
> Gesendet: Sonntag, 30. Juni 2002 21:19
> An: popa3d-users@...ts.openwall.com
> Betreff: Re: logging problems...
> 
> 
> On Sun, Jun 30, 2002 at 09:07:07PM +0200, Andi wrote:
> > --> 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?
> 
> The old package you don't have to touch.  You may just build popa3d
> from source, without producing a package out of it.  Just download the
> original popa3d source tarball and follow the instructions in INSTALL.
> Among the instructions it says to review and edit params.h, which you
> need to do.  Allocate a unique facility to popa3d, say, LOG_LOCAL0.
> Then use the newly built popa3d binary instead of the one that came
> with Slackware (edit the inetd.conf line).  Finally, edit syslog.conf
> to route the local0 facility wherever you like.
> 
> If this is still too complicated for you, then this list is probably
> not the right place for further questions on how to setup logging as
> that would be in no way specific to popa3d.
> 
> --
> /sd

-- 
/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.