Page MenuHomeFreeBSD

syslogd: allow network and local messages to use different formats
AcceptedPublic

Authored by wollman on Jun 20 2020, 8:06 PM.
Referenced Files
Unknown Object (File)
Sun, Apr 7, 10:30 AM
Unknown Object (File)
Dec 23 2023, 12:23 PM
Unknown Object (File)
Dec 13 2023, 3:34 AM
Unknown Object (File)
Nov 6 2023, 6:34 PM
Unknown Object (File)
Nov 4 2023, 6:02 AM
Unknown Object (File)
Oct 5 2023, 5:30 PM
Unknown Object (File)
Oct 3 2023, 6:00 AM
Unknown Object (File)
Aug 9 2023, 10:58 AM

Details

Reviewers
ed
pauamma_gundo.com
Group Reviewers
manpages
Summary

I need to be able to submit logs to a log server in RFC5424 format, but I don't want to change the format of local log files. I added a -r option that controls only the format of network destinations. I've given up my commit bit, so if this is accepted I'll be trying to recruit a src committer to push this.

Test Plan

We're running this in production now, sending to a graylog server, and once my colleagues who manage that service fix it so I can access it again, I'll be making sure that the messages are getting received an parsed properly.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 31845

Event Timeline

bcr added a subscriber: bcr.

OK from manpages.

I rewrote this to use an enum for the format type rather than a boolean, making it more flexible in the future. Will re-upload some day.

Restructured to use an enum for output formats rather than a bool, making it easier to change the defaults or add additional formats in the future. This was rebased onto 13.2 as a part of our migration; I haven't checked whether it still applies to 14-current.

In our repo this is two separate commits, one for adding the enum and a second for the -r option. Anyone who wants to commit this, I'd be happy to provide git format-patch format.

This revision is now accepted and ready to land.Aug 21 2023, 6:11 PM