Subject: misc/20733: would like a new feature with syslogd
To: None <gnats-bugs@gnats.netbsd.org>
From: None <bsdneophyte@yahoo.com>
List: netbsd-bugs
Date: 03/15/2003 19:21:40
>Number: 20733
>Category: misc
>Synopsis: would like a new feature with syslogd
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: misc-bug-people
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sat Mar 15 19:22:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Sameer
>Release: NetBSD 1.6
>Organization:
none
>Environment:
NetBSD pluto 1.6 NetBSD 1.6 (FROGGIE2) #0: Thu Mar 13 05:33:44 PST 2003 austin@pluto:/usr/src/sys/arch/sparc/compile/FROGGIE2 sparc
>Description:
It's not a problem, more something I'd like to see.
In FreeBSD you can isolate each syslog level to a specific file, instead of outputting every level above the specified level. I know this is a bad explanation, so I'll give an example.
local0.alert /var/log/local0
will write alert and emergency levels to /var/log/local0
If you need to evaluate the output for every single level, /var/log/local0 will become very unmanagable. Hoever, with FreeBSD you can do the following:
local0.=alert /var/log/local0
This will only direct the alert level messages to /var/log/local0, making things much more managable.
This would be a nice feature to have in NetBSD.
Another feature that would be nice is the syslogd "-a" feature. this allows syslog to record message from specific devices. So "syslogd -a 192.168.1.1/24" will take only messages from that IP address and not take messages from any other IP address.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: