Package Details: molly-guard 0.8.1-1

Git Clone URL: https://aur.archlinux.org/molly-guard.git (read-only, click to copy)
Package Base: molly-guard
Description: protects machines from accidental shutdowns/reboots (via ssh)
Upstream URL: https://packages.debian.org/stable/molly-guard
Licenses: Artistic2.0
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 14
Popularity: 0.25
First Submitted: 2009-03-01 20:30 (UTC)
Last Updated: 2023-11-13 12:47 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

mykhal commented on 2015-08-18 13:53 (UTC)

WARNING: installing molly-guard (version 0.5.1-2 in my case) might cause your machine to be unable to boot. The package is in conflict with systemd-sysvcompat, so it had to be removed. So "reboot" and "shutdown" commands disappeared. I had to reboot the system with "systemctl reboot". Then, the system did not boot up, because /sbin/init missing. I recovered by booting with init=/lib/systemd/systemd kernel param, uninstalling molly-guard and installing systemd-sysvcompat again.

tomasstorck commented on 2015-01-09 01:59 (UTC)

Thanks for the swift response :) Just tried the updated PKGBUILD. Haven't restarted, but I can already see that /sbin/init is missing. I suppose something could go wrong with the sed magic at work, but that stuff is way over my head.

mortzu commented on 2015-01-08 17:57 (UTC)

What about this: https://open.tf/~mortzu/files/molly-guard-0.5.1-2.src.tar.gz

kritztopf commented on 2015-01-08 13:41 (UTC)

I bumped molly-guard to the latest version. Inspecting the contents of the package does not yield any hint for overwriting /sbin/init or something along those lines. molly-guard itself has not coped well with the change to systemd and the /usr/bin-merge, so maybe it is time to drop this package completely. @ooijevaer: please tell me, if this package works for you now.

tomasstorck commented on 2015-01-08 11:22 (UTC)

Something is *very* wrong. Installation with all the defaults causes /sbin/init to disappear on both my machines, leading to the error at boot: "ERROR: Root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on your own. Good luck." In case anyone runs into this, you'll need to: * chroot into your installation (chroot new_root) * remove molly-guard (pacman -Rsc molly-guard) * recreate the link for /sbin/init as a workaround (ln ../lib/systemd/systemd /sbin/init) At this point you should be able to boot, but shutdown and all other commands overwritten by molly-guard are still lost and /usr/bin/init is not a link but a file. To fix this, after rebooting: * remove /usr/bin/init (mv /usr/bin/init{,.bu}) * reinstall base and base-devel (pacman -S base base-devel) kritztopf, are you still maintaining this package and can you reproduce this? I'll file for deletion if I don't hear back in a couple days.

fukawi2 commented on 2013-06-04 01:05 (UTC)

Please update PKGBUILD to install binaries to /usr/bin instead of /usr/sbin in line with recent changes: https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/

kritztopf commented on 2012-06-29 20:25 (UTC)

Fixed that issue, the Makefile is just awful -.- $pkgdir got inserted into some scripts by the Makefile

allspark commented on 2012-06-29 19:07 (UTC)

something is wrong on reboot i get this message: run-parts: failed to open directory /tmp/yaourt-tmp-allspark/aur-molly-guard/pkg/etc/molly-guard/run.d: No such file or directory

« First ‹ Previous 1 2 3 Next › Last »