npub1a3hfcvq3wa9zggsur737r9j095kh76rqy46we58jzu345xl4n3eqz9m44m (npub1a3h…m44m) I have always considered the "programs should log to stdout / stderr" approach simpler to implement, operate and reason around.
After reading your article, I see that logging to stdout and using syslog are not incompatible at all. A daemon can log to stdout (using syslog format), and the service manager can pipe this into /dev/log.
This combines the "easy to implement and use" benefits of printing to stdout, along with all the features of logging to syslog.
Hugo /
npub1rj…58qa2
2023-12-11 22:10:32
in reply to nevent1q…l2en
Author Public Key
npub1rjgkuvfx09dmp4dwsel9jrx2das7wdvhvfj862z8gfaj8d2pup9sf58qa2Published at
2023-12-11 22:10:32Event JSON
{
"id": "ed8b0cf3eea0ced1cc1ddeab1c6844c8c2af039cc3c5fcde126d38c98512f426",
"pubkey": "1c916e3126795bb0d5ae867e590cca6f61e7359762647d2847427b23b541e04b",
"created_at": 1702332632,
"kind": 1,
"tags": [
[
"p",
"ec6e9c3011774a24221c1fa3e1964f2d2d7f68602574ecd0f217235a1bf59c72",
"wss://relay.mostr.pub"
],
[
"p",
"579852afc54f2f4b992d5c48441d63f6545c530a7371764b6e67325d585ea6a1",
"wss://relay.mostr.pub"
],
[
"e",
"6656ccb4827c95e7c2ba6bd463e297f41fae5f222f7e79d5211478506b520a9c",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/whynothugo/statuses/111564071436256817",
"activitypub"
]
],
"content": "nostr:npub1a3hfcvq3wa9zggsur737r9j095kh76rqy46we58jzu345xl4n3eqz9m44m I have always considered the \"programs should log to stdout / stderr\" approach simpler to implement, operate and reason around.\n\nAfter reading your article, I see that logging to stdout and using syslog are not incompatible at all. A daemon can log to stdout (using syslog format), and the service manager can pipe this into /dev/log.\n\nThis combines the \"easy to implement and use\" benefits of printing to stdout, along with all the features of logging to syslog.",
"sig": "fc4e6962e4b528c7ca8c0d2b4559d4b7d15f399d321455879fbf4254408e10f0a92e7135fb1f7e2082f3002e9d3841d36347b4f3215090dbf562379fe18da759"
}