Package: molly-guard
Version: 0.6.4
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Reboot triggered by a collegue A, while an other collegue B was loged in
* What exactly did you do (or not do) that was effective (or
ineffective)?
Collegue A run "reboot".
* What was the outcome of this action?
System rebooted.
* What outcome did you expect instead?
Would have been nice, if molly-guard had asked collegue A wheter it is
OK to reboot.
Not yet a patch, but an idea, how that might work:
USERS=$(who | grep -v $( whoami ) )
if [ -n "$USERS" ] ;
then
echo -e "Following other users are loged in:\n$USERS\n\nAre you sure to
reboot?"
fi
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages molly-guard depends on:
ii procps 2:3.3.12-3+deb9u1
molly-guard recommends no packages.
molly-guard suggests no packages.
-- no debconf information
