Let me ask again with more details. I'm trying to kill this message placed in /var/log/messages. This is not the statistics created by the -s flag in inetd.cong. May 25 20:52:45 mardy popper[19426]: connect from 192.168.0.98 man popper says: On systems with BSD 4.3 syslogging, the server logs (by default) to the "local0" facility at priority "notice" But running syslogd in debugging mode shows: logmsg: authpriv.info<86>, flags 2, from mardy, msg May 26 16:33:14 popper[25004]: connect from 192.168.0.98 SO, I tried this in syslog.conf: authpriv.info -/var/log/popper And that indeed logs to that file, but it also still logs to /var/log/messages. I must be missing something in the syslog.conf setup still. I'd like to be able to just stop popper from logging instead of all authpriv.info messages. Any ideas? Thanks very much, Bill Moseley mailto:moseley@hank.org -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Bill Moseley wrote:
Let me ask again with more details. I'm trying to kill this message placed in /var/log/messages. This is not the statistics created by the -s flag in inetd.cong.
May 25 20:52:45 mardy popper[19426]: connect from 192.168.0.98
man popper says: On systems with BSD 4.3 syslogging, the server logs (by default) to the "local0" facility at priority "notice"
But running syslogd in debugging mode shows:
logmsg: authpriv.info<86>, flags 2, from mardy, msg May 26 16:33:14 popper[25004]: connect from 192.168.0.98
SO, I tried this in syslog.conf:
authpriv.info -/var/log/popper
And that indeed logs to that file, but it also still logs to /var/log/messages. I must be missing something in the syslog.conf setup still.
I'd like to be able to just stop popper from logging instead of all authpriv.info messages.
Any ideas?
Hi Bill, at least I got some vague idea. Have a look at /etc/syslog.conf, the configuration file for the syslog deamon. Very basicly, there are different "sources" and "severeties" that can be set up for logging. Work yourself through "man logger" and "man syslog.conf". I can't tell that the solution, but I assume this beeing helpful. Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
juergen.braukmann@ruhr-west.de
-
moseley@hank.org