DHCPD to log to another log file
Randall C Grimshaw
rgrimsha at syr.edu
Fri Jan 30 13:50:28 UTC 2009
I have been playing with this myself and the best solution so far is to log at level error. Then in syslog define (i.e.) local3.error in addition to the usual log, but to a different destination. The error messages will still appear in the usual info level log too, but the error level log has less background noise. I format the log() messages with fieldnames such as MACaddress= and IPnumber= which are then indexed by splunk.
From: dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-bounces at lists.isc.org] On Behalf Of Jessica Meyer
Sent: Friday, January 30, 2009 3:00 AM
To: dhcp-users at lists.isc.org
Subject: DHCPD to log to another log file
I have read a lot about DHCP logging, although I'm missing information
about DHCP logging. I know that DHCPD logs to syslog per default, and
this works great. But what I need is a "custom log" of just a limited
set of information (using the log() function).
Am I able to configure a second, independent log for this case? So
I've nothing against logging in syslogd, but I need a "clean" file
with just the information i want.
Any help is highly appreciated!
dhcp-users mailing list
dhcp-users at lists.isc.org
More information about the dhcp-users