Am 22.07.2014 13:23, schrieb Michael Biebl: > Am 22.07.2014 09:45, schrieb Johannes Schauer: >> Secondly, it is not very helpful to have the emergency mode message >> spawn in an (seemingly) infinite loop. I should not have to boot with >> init=/bin/bash. Instead, the emergency mode should start and allow me to >> analyze the situation. > > Samuel filed #755581 which seems to be the same issue about the > failing/looping emergency mode. I'd say we track this issue there.
Johannes, it seems that we tracked this issue down. Sorry it took so long. The problem is an active syslog.socket when emergency mode is entered. Each log message then tries to start rsyslog.service which conflicts with the emerge service (due to the dependencies rsyslog.service has). We need to make sure that syslog.socket is stopped when the emergency mode is entered. Adding Conflicts=syslog.socket to emergency.service [1] seems to be an acceptable workaround. It would be great if you can confirm that this also fixes the problem of the failing emergency mode for you. Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755672#30 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
