Okay, I finally understand #OpenBSD's syslogd. I still prefer #OpenRC's `output_log` and `error_log` parametes though.
I've never been a fan of having one monolithic (Or in syslog's case, a few monolithic) log files. Atleast it's not as bad as #systemd's binary log file with journalctl imo
I like just managing plaintext files, and it's a bit annoying having to configure syslog.conf to put each daemon's output into it's own log file.
Charadon /
npub1dd…52xy5
2024-06-26 17:17:24
Author Public Key
npub1ddy05srepxx6su7s7ddzwtjywfn4mwv5jrf7xyyygcdg5gt4uvgq252xy5Published at
2024-06-26 17:17:24Event JSON
{
"id": "f88445ac36c9d4bb585a175f20bb914597d8575f9e2ec1f8d657c5b56ff4782f",
"pubkey": "6b48fa4079098da873d0f35a272e4472675db99490d3e31084461a8a2175e310",
"created_at": 1719422244,
"kind": 1,
"tags": [
[
"t",
"openbsd"
],
[
"t",
"openrc"
],
[
"t",
"systemd"
],
[
"proxy",
"https://8bit.red/users/charadon/statuses/112684056200900968",
"activitypub"
]
],
"content": "Okay, I finally understand #OpenBSD's syslogd. I still prefer #OpenRC's `output_log` and `error_log` parametes though.\n\nI've never been a fan of having one monolithic (Or in syslog's case, a few monolithic) log files. Atleast it's not as bad as #systemd's binary log file with journalctl imo\n\nI like just managing plaintext files, and it's a bit annoying having to configure syslog.conf to put each daemon's output into it's own log file.",
"sig": "b5b510e648a7ceca1c7bdb625b36a83cf90f48833a6780cff011b4ac4ad0f59f58f43f9fa52d9376ce49d397a749e45fcf55529fe04a8228a15f1a6562688b2a"
}