I never said it was a drop-in replacement.
But if the goal is to use this instead of "sudo", some migration documentation
would help quite a bit.
I know the implementation will not work with current "sudoers" configurations,
nor will it ever per comments from Leonard Poettering.
But the curren
run0 is not a drop-in replacement for sudo in every case. It works
inherently different but therein lies its strength (but also its
weaknesses). For allowing only specific commands you will need to look
into setting up polkit rules because that is what run0 uses in the
back to check if running the
I have attempted to use systemd-journald as a centralized log collector, it
works fine and the interface provided by journalctl is very convenient to
quickly find things, following logs and other things.
But I quickly discovered the performance implications of doing so, as when
the journal gets ov
run0' is defined as a better 'sudo', though the documentation I see is a bit
sparse.
Is documentation regarding how to get similiar function from 'run0' as you can
in a sudo configuration file present anywhere?
Primary issue is restricting access to specific users and commands.
The latter is t
