<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [systemd] keyboard shortcut to show jobs during boot
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bsystemd%5D%20keyboard%20shortcut%20to%20show%20jobs%20during%20boot&In-Reply-To=%3C201204072122.35709.alien%40rmail.be%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="014096.html">
<LINK REL="Next" HREF="014006.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [systemd] keyboard shortcut to show jobs during boot</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bsystemd%5D%20keyboard%20shortcut%20to%20show%20jobs%20during%20boot&In-Reply-To=%3C201204072122.35709.alien%40rmail.be%3E"
TITLE="[Mageia-dev] [systemd] keyboard shortcut to show jobs during boot">alien at rmail.be
</A><BR>
<I>Sat Apr 7 21:22:35 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="014096.html">[Mageia-dev] painful discussion n°1: debloating
</A></li>
<LI>Next message: <A HREF="014006.html">[Mageia-dev] Freeze push: drakx-installer-binaries
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14002">[ date ]</a>
<a href="thread.html#14002">[ thread ]</a>
<a href="subject.html#14002">[ subject ]</a>
<a href="author.html#14002">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>in order to investigate hangs or slow boots or whatever, it would be useful to
have some kind of key combination that lists the current systemd jobs and
where it's hanging/waiting or whatever
either that or detect a hang an spawn some kind of emergency login somewhere
actually, if i'm really pulling out my want-to-have book, howabout a tty that
(until it can actually get a tty), shows an top like watch of current jobs in
systemd, where you can force some kind of process, ie: killing it, or letting
all the dependant ones go through.
perhaps that could be on the tty that would eventually always become a tty (as
i remember we talked about)
let's say that tty12 gets the kernel logging, then tty11 could show first
dracut/udev stuff, then proceed with systemd jobs, and when it can get a tty,
to be reserved for tty. (all the others could be reserved for graphicals then)
that way, no matter what happens, you get some nice info/tty availability.
ok, give all this nice-to-have...
is there a way we can find out why a boot hangs? is there some logging we can
check in a rescue or ...?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="014096.html">[Mageia-dev] painful discussion n°1: debloating
</A></li>
<LI>Next message: <A HREF="014006.html">[Mageia-dev] Freeze push: drakx-installer-binaries
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14002">[ date ]</a>
<a href="thread.html#14002">[ thread ]</a>
<a href="subject.html#14002">[ subject ]</a>
<a href="author.html#14002">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>