Package Details: molly-guard 0.7.2-4

Git Clone URL: (read-only, click to copy)
Package Base: molly-guard
Description: protects machines from accidental shutdowns/reboots (via ssh)
Upstream URL:
Licenses: Artistic2.0
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 13
Popularity: 0.000003
First Submitted: 2009-03-01 20:30 (UTC)
Last Updated: 2022-10-17 09:59 (UTC)

Latest Comments

1 2 Next › Last »

francoism90 commented on 2018-03-19 15:41 (UTC)

How does this work? It doesn't do anything for me for some reason.

strubbl commented on 2018-02-07 18:34 (UTC) (edited on 2018-02-07 18:35 (UTC) by strubbl)

checksum failure:

==> Continue building molly-guard ? [Y/n]
==> -------------------------------------

==> Building and installing package
==> Making package: molly-guard 0.7.1-1 (Wed Feb  7 19:34:10 CET 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading molly-guard_0.7.1.tar.xz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 12860  100 12860    0     0   169k      0 --:--:-- --:--:-- --:--:--  169k
  -> Found
==> Validating source files with sha256sums...
    molly-guard_0.7.1.tar.xz ... Passed ... Passed
==> Validating source files with sha512sums...
    molly-guard_0.7.1.tar.xz ... FAILED ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build molly-guard.
==> Restart building molly-guard ? [y/N]
==> ------------------------------------

mortzu commented on 2015-08-20 18:48 (UTC)

I'll fix it

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:

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.