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
Hi!
this does NOT work. You have to uncomment the output lines in the popper code and recompile it.
Hi.
How can I stop the popper from logging every user access, even when the user did only check to see if there were any new mails. This seems
hardly the kind of information that needs to be logged every time...
Bye,
Jürgen
According to the manpage, just remove the "-s" from the line in /etc/inetd.conf and restart/hangup inetd.
-- "Soap and education are not as sudden as a massacre, but they are more deadly in the long run." - Mark Twain