You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a munged option to terminate after the daemon has been idle for a specified duration of time (maybe --idle-timeout). When combined with systemd socket activation (#83), munged could be started on demand and automatically terminate shortly thereafter, allowing the process to run only when needed.
This option would also be very useful for running munged in the test suite. If a test fails and a munged process running in the background is not terminated, the test suite script will hang at the end. Clearly, this is not desired behavior when the test suite is run in an automated manner.
Add a
munged
option to terminate after the daemon has been idle for a specified duration of time (maybe--idle-timeout
). When combined with systemd socket activation (#83),munged
could be started on demand and automatically terminate shortly thereafter, allowing the process to run only when needed.This option would also be very useful for running
munged
in the test suite. If a test fails and amunged
process running in the background is not terminated, the test suite script will hang at the end. Clearly, this is not desired behavior when the test suite is run in an automated manner.See #53 for the initial rationale.
The text was updated successfully, but these errors were encountered: