Mailinglist Archive: opensuse-security (601 mails)

[Roman Drahtmueller <draht@xxxxxxx>]

> Hello again!
> 
> Indeed, the suggested solution does not work!
> But there has to be a better way than rebuild the popper!
> Problem is: I couldn't find the output line in the popper source. Could
> it be that inetd is doing this log, before calling popper???
> But I surely son't want to rebuild the inetd!
> 
> Doesn't anybody else experience this problem that popper is cluttering
> the /var/log/messages file?
> 
> There *must* be a way to stop this logging-call. Perhaps by configuring
> syslogd???
> 
>     Jürgen

To clear this up:

There are possibly two lines per connection in your syslogs:

Aug 27 08:36:32 para popper[10193]: connect from 127.0.0.1 (127.0.0.1)
Aug 27 08:37:01 para popper[10193]: Stats: shotdead 1 415 0 0


The first line is from /usr/sbin/tcpd (the tcp wrapper) in
/etc/inetd.conf. It's not the popper program's fault - in fact, it doesn't
even know that tcpd wrote a log since it was started from him.

The second line vanishes if you remove the "-s" from the popper line in
/etc/inetd.conf. This works, you find the relevant code in pop_updt.c:86
and pop_log.c.

Thanks,
Roman.
-- 
 -                                                                      -
| Roman Drahtmüller      <draht@xxxxxxx> //          "Caution: Cape does |
  SuSE GmbH - Security           Phone: //       not enable user to fly."
| Nürnberg, Germany     +49-911-740530 // (Batman Costume warning label) |
 -                                                                      -