Page MenuHomeFreeBSD

newsyslog: provide -I option to specify default signal
ClosedPublic

Authored by glebius on Sep 23 2025, 8:11 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 22, 1:40 PM
Unknown Object (File)
Wed, Nov 5, 4:42 PM
Unknown Object (File)
Wed, Nov 5, 9:40 AM
Unknown Object (File)
Wed, Nov 5, 9:40 AM
Unknown Object (File)
Wed, Nov 5, 9:39 AM
Unknown Object (File)
Wed, Nov 5, 9:38 AM
Unknown Object (File)
Wed, Nov 5, 9:33 AM
Unknown Object (File)
Sat, Oct 25, 4:35 PM
Subscribers

Details

Summary

Useful when used with syslog-ng, which uses SIGUSR1. Instead of adding
signal number to every new entry, just set it via command line option.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 67304
Build 64187: arc lint + arc unit

Event Timeline

Minor language corrections in the man page.

usr.sbin/newsyslog/newsyslog.8
252

s/don't/do not/
s/have signal/have a signal/

253

This option accepts either a signal number or a name as argument.

254

s/Default/The default/

Thanks, ready to commit from my point of view.

This revision is now accepted and ready to land.Sep 25 2025, 11:15 AM

I like the change in general, but if I was you I'd probably use getopt_long() and call the option --signal (consider this as an optional suggestion; I don't have strong opinion with this choice), because -I was somewhat counterintuitive to me as a flag to specify signal and both -s and -S were already occupied.

I like the change in general, but if I was you I'd probably use getopt_long() and call the option --signal (consider this as an optional suggestion; I don't have strong opinion with this choice), because -I was somewhat counterintuitive to me as a flag to specify signal and both -s and -S were already occupied.

i don't think we should be introducing mandatory non-standard GNU long options into base unless it's for compatibility with other platforms.