On Wed, 28.01.15 02:02, Lennart Poettering (lenn...@poettering.net) wrote: > On Mon, 19.01.15 17:59, Felix Miata (mrma...@earthlink.net) wrote: > > > Has anything been done in more recent releases about this? I do a lot of > > cloning, and sometimes produce typos on grub cmdlines and fstab lines. This > > produces long delays in init followed by emergency mode when the > > non-essential mount fails and fstab for that device does not include the > > nofail option. When I recognize early in init that I have made a fstab typo, > > I try to CAD to choose another boot choice that isn't broken and fix the > > typo, but that produces yet another start job wait for the same broken job, > > often followed by a gazillion failed to save sound card state messages from > > holding down CAD. > > > > openSUSEes, Mageias & Fedoras (including Factories, Cauldrons & Rawhides) > > comprise most of my installations subject to these self-inflicted delays > > that > > I can't recall being a problem with sysvinit. > > Hmm, so there has been a long-standing TODO list item to show some job > data when C-a-d is pressed 3 times within 1s, and reboot the machine > immediately on 3 times within 10s or so. I figure that would already > make you happy?
So, I actually implemented this now. Or actually, I only implemented the part about C-A-D triggering a reboot. I picked 7x per 2s as limit though, seemed easier to me. It should be easy to extend this to show information about running jobs after 3x too. http://cgit.freedesktop.org/systemd/systemd/commit/?id=2e5c94b9aaefce46835b623e800cfc168995ea3f Hope this is useful, Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel