diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017642.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-July/017642.html | 192 |
1 files changed, 192 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017642.html b/zarb-ml/mageia-dev/2012-July/017642.html new file mode 100644 index 000000000..d63106ed7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-July/017642.html @@ -0,0 +1,192 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Systemd improvement + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Systemd%20improvement&In-Reply-To=%3C500E7126.6010205%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="017640.html"> + <LINK REL="Next" HREF="017648.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Systemd improvement</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Systemd%20improvement&In-Reply-To=%3C500E7126.6010205%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] Systemd improvement">mageia at colin.guthr.ie + </A><BR> + <I>Tue Jul 24 11:55:50 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="017640.html">[Mageia-dev] Systemd improvement +</A></li> + <LI>Next message: <A HREF="017648.html">[Mageia-dev] Systemd improvement +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17642">[ date ]</a> + <a href="thread.html#17642">[ thread ]</a> + <a href="subject.html#17642">[ subject ]</a> + <a href="author.html#17642">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Olivier Thauvin at 24/07/12 10:47 did gyre and gimble: +><i> * Colin Guthrie (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>) wrote: +</I>>><i> 'Twas brillig, and Olivier Thauvin at 24/07/12 10:02 did gyre and gimble: +</I>>>><i> I have some minor issues with systemd so I report it in case some +</I>>>><i> improvment could be done: +</I>>>><i> +</I>>>><i> 1) The timeout is very long when the system failed to ask the passphrase +</I>>>><i> for encrypted partition, os it is very long to reach any console (this +</I>>>><i> happend only when there is a problem) +</I>>>><i> +</I>>>><i> 2) When everything work fine, the timeout occur if the passphrase for +</I>>>><i> encrypted partition is not enter early enough: I power up my laptop, do +</I>>>><i> something else, come back and it report the boot has failed, surprising! +</I>>><i> +</I>>><i> So it's both too long and too short :) +</I>>><i> +</I>>><i> I'm not sure how to deal with this, but I would suggest that we need to +</I>>><i> do something a bit more creative to deal with your particular use case. +</I>>><i> +</I>>><i> For yourself, it's not a "critical" filesystem - e.g. it's not /usr or +</I>>><i> similar, but /home. +</I>><i> +</I>><i> No you misunderstood, if the system succeed to launch +</I>><i> '/usr/bin/ask-the-passphrase' or whatever its name is, it must wait an +</I>><i> answer for ever and not continue booting and finally claim "hey +</I>><i> surprising, I failed to boot w/o the passphrase". +</I>><i> The firest time it happend I really thought my system was broken. +</I> +So what if you cannot enter your password and want to rescue the system? +Should it still wait forever until you enter your passphrase? Or would +you have to deliberately enter your passphrase wrong X number of times +to get the the rescue mode? + +><i> However, if it cannot launch '/usr/bin/ask-the-passphrase' it is sure +</I>><i> booting will failed as it cannot get the passphrase, no need to wait an +</I>><i> impossible user input. +</I>><i> Again, the case I just talk about happend only in case of bug and must +</I>><i> not happend on stable distro. +</I> +In this particular case it was not that it could not run the password +prompt, simply that it didn't know how to mount something completely +alien to it. + +You have to remember that all this is happening completely +asynchronously these days. It's not like systemd is specifically poking +things and failing. It's waiting for the system to do it itself, hence +the timeouts. + +That's not to say this can't be solved, it's just that we're treating +one mount much like any other - and some mounts take a loooooong time to +happen (e.g. just try recent btrfs stuff with all the krud it does when +mounting). + +But the "waiting-for-password" case and the "there is no subsystem to +handle even asking for the password" case are essentially treated the +same way. + +This is likely a discussion to take to the upstream mailing list. + +>>><i> 3) the boot process hang/stop/wait if my wireless card is down (using +</I>>>><i> the hardware switch on the side of my laptop). This step need just one +</I>>>><i> second when the card is on, even it does not connect to any network. +</I>>><i> +</I>>><i> If you have any NFS (or other network mounts) mounts that are NOT marked +</I>>><i> with nofail, then we consider them to be "critical" filesystems. If +</I>>><i> these filesystems are NOT needed for boot, then just mark them as +</I>>><i> "nofail" and they will still be mounted but your DM/logins will not be +</I>>><i> delayed while waiting for the network. +</I>><i> +</I>><i> +</I>><i> I don't have nfs in my fstab but maybe this is triggered by another +</I>><i> service. +</I>><i> But I don't see the point of waiting the card to be on, especially when +</I>><i> the card is on it don't connect to any network and don't wait this +</I>><i> happend. +</I> +Hmm in that case it sounds like a different issue than the deliberate +stuff that waits for the network to be ready. + +Do you know which bit of the system is waiting for this? Is it +network-up.service or something else? (I doubt it can be network-up as +this shouldn't delay logins unless the afore mentioned NFS mounts are +present) + +Col + + + + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="017640.html">[Mageia-dev] Systemd improvement +</A></li> + <LI>Next message: <A HREF="017648.html">[Mageia-dev] Systemd improvement +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17642">[ date ]</a> + <a href="thread.html#17642">[ thread ]</a> + <a href="subject.html#17642">[ subject ]</a> + <a href="author.html#17642">[ 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> |