Red Hat

Hello
I was getting hammered in /var/log/messages from snmpd becouse it was running a jira which was sending email everytime someone updated a case or made any changes.
Therefor I decided to turn down the loglvl of snmpd, so what I did was add

Code:

snmpd.notice;

to

Code:

 [root@jira ~]# cat /etc/syslog.conf
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.*                                                 /dev/console

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;snmpd.notice;mail.none;authpriv.none;cron.none           /var/log/messages

From googeling I am under the impression that setting log lvl to notice will give me notice and all lvls above to /var/log/messages. err, crit and so on...

After editing I did

Code:

[root@jira ~]# service syslog restart
Shutting down kernel logger:                               [  OK  ]
Shutting down system logger:                               [  OK  ]
Starting system logger:                                    [  OK  ]
Starting kernel logger:                                    [  OK  ]

Now here is a something I'am a bit worried about
After restarting syslogd
This is my last entrie in messages:

Code:

Mar  8 16:17:58 jira kernel: Kernel logging (proc) stopped.
Mar  8 16:17:58 jira kernel: Kernel log daemon terminating.
Mar  8 16:18:00 jira exiting on signal 15

Now little over two hours later there are no new entries in the /var/log/messages. This could be fine since messages was basically filled with snmpd messages and nothing more. Just that those last three entries got me a bit nervus. Any thoughts on this? Is there a smooth way to send a test message to syslog from terminal or something to just see if everything is as it should?

See man logger, listed on man syslog() ?

solved it