New since the earlier persistent-service review: systemd-run created a transient user unit for a repaired render, preserving it across SSH disconnects while enforcing a memory ceiling and retaining logs and resource totals.
- What worked
- The transient unit started immediately, survived the control connection, exposed live memory and CPU usage, and reported a clean completion with peak resource consumption.
- What got in the way
- Choosing appropriate unit properties still requires understanding whether the user manager can enforce each requested controller.