I'm unable to find out (on NOW) what facility and level disk quota exceeded messages are syslogged:
Sat Jan 29 23:01:53 PST [de0]: uid 14602: disk quota exceeded on volume vol0
I don't want to see them in general...however I'm wary of missing other stuff. I currently have:
*.info /dev/console *.warning /etc/messages *.err;kern.* @adminhost
which I presume should catch most interesting events apart from the the quota exceeded messages...
Advice is appreciated.
Thanks, Adi
They're logged to kern.notice, which you probably shouldn't suppress....
-----Original Message----- From: owner-dl-toasters@netapp.com [mailto:owner-dl-toasters@netapp.com]On Behalf Of R.P. Aditya Sent: Saturday, January 29, 2000 11:05 PM To: toasters@mathworks.com Subject: logging quota exceeded messages
I'm unable to find out (on NOW) what facility and level disk quota exceeded messages are syslogged:
Sat Jan 29 23:01:53 PST [de0]: uid 14602: disk quota exceeded on volume vol0
I don't want to see them in general...however I'm wary of missing other stuff. I currently have:
*.info /dev/console *.warning /etc/messages *.err;kern.* @adminhost
which I presume should catch most interesting events apart from the the quota exceeded messages...
Advice is appreciated.
Thanks, Adi
In message 000001bf6af2$1f2fcf00$350f960a@27702.netapp.com, "Matt Day" writes:
They're logged to kern.notice, which you probably shouldn't suppress....
so retaining kern.warning doesn't suffice? What else is logged at kern.notice that I might want to keep track of?
Thanks, Adi
-----Original Message----- From: owner-dl-toasters@netapp.com [mailto:owner-dl-toasters@netapp.com]On Behalf Of R.P. Aditya Sent: Saturday, January 29, 2000 11:05 PM To: toasters@mathworks.com Subject: logging quota exceeded messages
I'm unable to find out (on NOW) what facility and level disk quota exceeded messages are syslogged:
Sat Jan 29 23:01:53 PST [de0]: uid 14602: disk quota exceeded on volume vol0
I don't want to see them in general...however I'm wary of missing other stuff. I currently have:
*.info /dev/console *.warning /etc/messages *.err;kern.* @adminhost
which I presume should catch most interesting events apart from the the quota exceeded messages...
Advice is appreciated.
Thanks, Adi
In message 000001bf6af2$1f2fcf00$350f960a@27702.netapp.com, "Matt Day"
writes:
They're logged to kern.notice, which you probably shouldn't suppress....
so retaining kern.warning doesn't suffice? What else is logged at
kern.notice
that I might want to keep track of?
kern.notice is used quite a bit. Various status messages, especially from RAID and WAFL. If you want to filter kern.notice out, I recommend logging it to a separate file at least.