systemd-journald compatibility

[Weidav]

I know this repo hasn't seen any updates in a while, but it like the lightweight solution.
I recently migrated some of my overengineered services that run X times a day from docker to systemctl and this is one of them.

Usually I let systemd-journald manage the logs and check them with journalctl, but your script isn't compatible with it. When I use --log-console it throws this error:

cfddns.sh[3778639]: /usr/local/bin/cfddns.sh: 380: cannot create /dev/stdout: No such device or address

So for now i just use a logfile as suggested.

Is there a simple solution to this that I'm overlooking?
If not, than I'd look into this and see if I can make it compatible with both systemd-journald and a regular logfile.

[asifbacchus]

This script is due for an update, and you're quite correct, logging using systemd-journald would be a great feature! It does, however, involve totally changing the logging system used by the script.

The --log-console parameter was never really meant to be used while running as a systemd service. It was intended more for debugging. I think the best option would be to add a new switch, something like --log-journal, and then use a built-in utility like logger to send output to the journal with an appropriate identifier so it can be parsed, searched, etc.

I might have some time to work on this over the weekend. I'll keep this issue updated with any progress I make. Thanks for letting me know about this, and sorry you ran into this issue!

[Weidav]

Thanks for the quick response!

I think to switch completely to systemd-journald should be easy, althoug a bit annoying/repetitive work to replace all the log-calls. I have a systemd service that basically just uses echo for logging and it works out of the box with systemd-journald.

But keeping the logfile-option and adding the systemd-journald compatibility could be more tricky.

Anyways, thanks for your effort! Let me know if I can help!