Package: molly-guard Version: 0.7.2 Severity: wishlist Tags: patch Dear Maintainer,
While working on adding a snippet to molly-guard to check for running VMs and prompt if there are any, we discovered that the standard approach for systems managed by Ansible is to bypass molly-guard completely. See https://docs.ansible.com/ansible/8/collections/ansible/builtin/reboot_module.html and search for molly-guard. We use Ansible, and I think this sucks, as I want molly-guard to protect reboots for other situations. I have modified molly-guard to detect being run by Ansible and not ask questions, just exit 1 and refuse to take action. We have deployed this to some of our fleet and have found it to work fine. Would you please consider merging this change? Changes are here: https://salsa.debian.org/puck/molly-guard/-/commits/conf-mgmt This also includes patches for general housekeeping of the package. In addition, I have considered whether the prompt logic and sigh() should be moved into shutdown.in and allowed to be generic. I'd be interested to hear your thoughts, and I'd be happy to have a punt at that. Kind regards, Andrew -- System Information: Debian Release: 12.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 6.1.0-12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_AUX Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages molly-guard depends on: ii procps 2:4.0.2-3 molly-guard recommends no packages. molly-guard suggests no packages. -- no debconf information
