Live CDs/USBs, netbooted PCs and in some cases discardable VMs and containers, usually have a read only base image and an overlayfs/tmpfs/cow filesystem on top of them.

There, we want some services not to run, like package manager upgrades, certain cron-like jobs etc.

It would be awesome if upstream systemd documented what "constitutes a live mode", e.g. the presence of a /run/live directory

I've just set this up on a couple of old Cubox 1's running Arch Linux. If you could add onto the README.md that Arch uses systemd/Timers by default but installing a cronie as a package 'pacman -S cronie' followed by 'systemctl enable cronie', adds cron timers. All works fine.
Thanks for the useful utility.

I think the line:

$ journalctl --user-unit python_demo_service

should actually be:

journalctl _SYSTEMD_UNIT=python_demo_service.service

Or at least, that's what worked for me on a Raspberry Pi 4, running Buster (Raspian/Debbian). YLMV!

Rsdctl just pretty prints the returned json from rustysd. To make this an actually useful tool it needs to be better in presenting the retrieved info/results/errors.

Is it possible to add an option to remove '$HOME' (or perhaps a user specified prefix) from the list before displaying the files?

README seems to have a broken link for the original proposal, consider updating the link to the document or removing it altogether.

Thank you!

After running procsd create the services were not starting and I was receiving:

/bin/bash: -c: option requires an argument

It turns out that an argument is missing after the service file is generated. An exec should be added:

ExecStart=/bin/bash -lc 'exec $BINDIR/gunicorn app.wsgi --log-file=- -b 127.0.0.1:$PORT --log-level DEBUG'

It also the same in Foreman. procsd does no

Hi there, thanks for the useful library.

Perhaps it could be useful to include the YAML configuration docs in the README?

https://ngrok.com/docs#tunnel-definitions

This is in case someone wants to add some .yml configurations that aren't specified in your example config file. (I had to use this for example to look up remote_addr.

Thanks again!

Forced termination caused corruption of pos file. Mutations to pos file could be done atomically to increase reliability.

fluent-plugin-systemd version 1.0.1

From Logs

2018-07-05 07:02:41 +0000 [error]: [systemd.log] failed to read data from plugin storage file path="/var/log/systemd.log.pos" error_class=Yajl::ParseError error="lexical error: invalid char in json text.\n