2 hours ago · Tech · 0 comments

While the entire systemd project has historically been rather polarizing, I have found it to be easier to maintain for my own environments. When working on services on windows or MacOS , I have come to miss having journald when running services. MacOS launchd services let you StandardOutPath and StandardErrorPath, each application can set them to whatever path they want. While applications can directly use MacOS unified logging, I wanted to prototype an idea of launchd handling directing files. Since I can not (easily) modify launchd, I decided to write a redirect-output helper, to prototype how this might look. The goal, is that the running service itself, should not need to worry about stdout and stderr, similar to how applications running under systemd do not. This means we need to have a program to wrap our target. I decided on the following api for an example ~/Library/LaunchAgents/net.example.my-app.plist. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.