Skip to content

Use the “mail” syslog facility in the journal#91

Open
Hawk777 wants to merge 1 commit intobruceg:masterfrom
Hawk777:systemd-syslog-facility
Open

Use the “mail” syslog facility in the journal#91
Hawk777 wants to merge 1 commit intobruceg:masterfrom
Hawk777:systemd-syslog-facility

Conversation

@Hawk777
Copy link

@Hawk777 Hawk777 commented Dec 30, 2023

When running under systemd, what’s done with text the program prints to stdout/stderr depends on the StandardOutput and StandardError directives in the unit file. Those are unset in this unit file (which is probably appropriate), which means they inherit defaults from a global config file. If unset in that config file, in turn, the default is to write the messages to the system journal. When that is done, the journal entries are automatically given syslog-style metadata, i.e. an identifier, facility code, and priority level. If unspecified, the facility code is set to “daemon”; however, since nullmailer is in the business of handling e-mail, “mail” is a better choice out of the available set.

When running under systemd, what’s done with text the program prints to
stdout/stderr depends on the `StandardOutput` and `StandardError`
directives in the unit file. Those are unset in this unit file (which is
probably appropriate), which means they inherit defaults from a global
config file. If unset in that config file, in turn, the default is to
write the messages to the system journal. When that is done, the journal
entries are automatically given syslog-style metadata, i.e. an
identifier, facility code, and priority level. If unspecified, the
facility code is set to “daemon”; however, since nullmailer is in the
business of handling e-mail, “mail” is a better choice out of the
available set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant