[opensuse-factory] systemd or not systemd - todays bug?
Hello, I have two factory boot: one with systemd on the kernel command line, and the very same one, but without the option. after a today zypper dup (only complaining about some libreoffice library), the one with systemd option do not find the harddrive so no log), but the version without systemd boots perfectly That said, my /var/log/messages is full of systemd calls! (here the end: Sep 7 13:43:15 linux-lpd0 systemd[1]: Child 7672 died (code=exited, status=0/SUCCESS) Sep 7 13:43:15 linux-lpd0 systemd[1]: Child 7672 belongs to network.service Sep 7 13:43:15 linux-lpd0 systemd[1]: network.service: control process exited, code=exited status=0 Sep 7 13:43:15 linux-lpd0 systemd[1]: network.service got final SIGCHLD for state stop Sep 7 13:43:15 linux-lpd0 systemd[1]: network.service changed stop -> dead Sep 7 13:43:15 linux-lpd0 systemd[1]: Job network.service/stop finished, result=done Sep 7 13:43:15 linux-lpd0 kernel: Kernel logging (proc) stopped. Sep 7 13:43:15 linux-lpd0 rsyslogd: [origin software="rsyslogd" swVersion="5.8.4" x-pid="899" x-info="http://www.rsyslog.com"] exiting on signal 15. ) so I wonder if systemd is now default? if not may I fill a bug report for the other one (the one that stops at HDD not found) thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am 07.09.2011 15:04, schrieb jdd:
so I wonder if systemd is now default?
thanks jdd
I think so. Afair it was said so on this list some days ago. It is the same here too on my two factory-fed machines. So I don't think there is a reason to worry about it. Andreas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (2)
-
Freigeist
-
jdd