On 02/18/99 17:44:54 you wrote:
Does anyone else have an interest in having the flexibility of including soft error messages in the log files or is there a general consensus that they are unnecessary. We're trying to get support from other users for making the toggle available.
Yes, I would like to have the toggle as well. In the first place, I would like those messages to remain in the log file (I have not upgraded to 5.1 yet but plan to do so next month). We have prevented disk crashes by monitoring them.
The toggle *should* already be in place. The messages should be logged at the syslog DEBUG level. If you specify a higher level, you shouldn't see them.
One argument against this is there's a lot of other junk that can get logged at the DEBUG level. All this means is that some priorities need to be reorganized, and an acceptable default level found. Or you could break them up through useful facility designations. And simply inform old customers who may have turned on DEBUG just for these messages what the recommendation is for the new version.
You don't see me criticizing netapp often, but I will here. They sometimes seem to bow to pressure to remove informational messages and options useful to "power users" in order to reduce the load on their support staff and keep up the appearance of simplicity. This seems to be what happened here. I also think it's pretty poor of them to make the change without telling their customers (was it documented?), or without even asking if that's what their customers wanted.
Bruce
The toggle *should* already be in place. The messages should be logged at the syslog DEBUG level. If you specify a higher level, you shouldn't see them.
One argument against this is there's a lot of other junk that can get logged at the DEBUG level. All this means is that some priorities need to be reorganized, and an acceptable default level found. Or you could
Hmm.
Perhaps not everybody here at NetApp is aware that "syslog" on our boxes has the same 8 severity levels that it has had on UNIX boxes for ages (not surprising, given that it can send messages to remote UNIX syslog daemons), and that one might, for example, choose to log them at the WARNING or NOTICE or INFO level.
(Then again, I suspect the same applies to much of the UNIX world - people generally seem to log just at LOG_ERR level.)
That way, you could see them if you set the level properly, but wouldn't get spammed with the DEBUG level crap.
Or you could break them up through useful facility designations.
Unfortunately, we have the exact same facility codes as the UNIX "syslog", too, which means that, unless you resort to "local0" through "local7", it's not clear what facility codes would be useful.
-
guy＠netapp.com -
sirbruce＠ix.netcom.com