Project

General

Profile

Actions

Feature #150

closed

Option to change syslog facility

Added by Chris Buechler over 15 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
11/15/2009
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

(moved from cvstrac # 1740)
Is it possible to add the option of changing which syslog facility the firewall messages are sent on? It appears that it uses local0, but it would be nice to be able to customize it.


Files

syslog_facility_patch.rtf (4.67 KB) syslog_facility_patch.rtf Dan Swartzendruber, 12/22/2009 04:34 PM
Actions #1

Updated by Dan Swartzendruber over 15 years ago

Chris Buechler wrote:

(moved from cvstrac # 1740)
Is it possible to add the option of changing which syslog facility the firewall messages are sent on? It appears that it uses local0, but it would be nice to be able to customize it.

Possible fix for this. I am not checking to see if the filter facility duplicates one of the fixed-purpose ones. If that is an issue, let me know. Also, I noticed after I generated the diff and shut down the VM, I probably should have moved the setting of the filterstr variable to after the 'isset' check just after it.

Actions #2

Updated by Chris Buechler over 15 years ago

  • Target version set to 2.1
Actions #3

Updated by Chris Buechler about 15 years ago

  • Target version changed from 2.1 to Future
Actions #4

Updated by Chris Buechler over 14 years ago

In addition to facility, everything comes through as "warning" currently where some logs should be marked as informational. May justify a separate ticket at some point but sort of along the same lines.

Actions #5

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Closed
  • Target version deleted (Future)

facility is partially how syslogd splits log files, not worth doing

Actions

Also available in: Atom PDF