Package Details: molly-guard 0.6.4-1

Git Clone URL: (read-only)
Package Base: molly-guard
Description: protects machines from accidental shutdowns/reboots (via ssh)
Upstream URL:
Licenses: Artistic2.0
Submitter: None
Maintainer: CarstenF
Last Packager: CarstenF
Votes: 12
Popularity: 0.004168
First Submitted: 2009-03-01 20:30
Last Updated: 2017-03-18 21:37

Latest Comments

mortzu commented on 2015-08-20 18:48

I'll fix it

mykhal commented on 2015-08-18 13:53

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.

mykhal commented on 2015-08-18 13:05

WARNING: do not install latest molly-guard 0.5.1-2, it will cripple your system and it will be unable to start after reboot

ooijevaer commented on 2015-01-09 01:59

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

What about this:

kritztopf commented on 2015-01-08 13:41

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.

ooijevaer commented on 2015-01-08 11:22

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.

roknir commented on 2013-11-07 01:28

$ sudo pacman -U molly-guard-0.4.5-4-any.pkg.tar.xz
loading packages...
resolving dependencies...
looking for inter-conflicts...
:: molly-guard and systemd-sysvcompat are in conflict. Remove systemd-sysvcompat? [y/N]

fukawi2 commented on 2013-06-04 01:05

Please update PKGBUILD to install binaries to /usr/bin instead of /usr/sbin in line with recent changes:

kritztopf commented on 2012-06-29 20:25

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

All comments