[Bug 712300] New: systemd: service startup order not blocking

newer
[Bug 709438] New: java can't be...

bugzilla_noreply＠novell.com

15 Aug 2011 15 Aug '11

18:04

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c0 Summary: systemd: service startup order not blocking Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: fcrozat@novell.com ReportedBy: dimstar@opensuse.org QAContact: qa@suse.de Found By: Community User Blocker: --- Seems a vast of users is seeing this issue: There are 'two' scenarios, this bug us about the '2nd one': 1) Boot takes 5 minutes (This is the 'known' NM_ONLINE_TIMEOUT) 2) Once NM_ONLINE_TIMEOUT is set to 0, the boot is 'fast' but it does not come up grapical. At least those two services are missing: NetworkManager.service xdm.service The issue for both is that they are started in parallel or before dbus is running. (NM is 'tried' to be started from /etc/init.d/network) and xdm is a 'traditional' start script anyway. As a result, the boot 'ends with a login' prompt. Logging in and then systemctl start NetworkManager.service systemctl start xdm.service brings up a fully functional Environment for me. (Perfectly suitable for me now as a workaround). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

15 Aug 15 Aug

18:10

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |696902 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:24

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c1 Bjørn Lie changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjorn.lie@gmail.com --- Comment #1 from Bjørn Lie 2011-08-15 20:24:54 CEST --- Try this. chkconfig -f network off systemctl enable NetworkManager.service Reboot btw systemd-analyze plot > filename.svg is a great tool to see whats taking so long. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:37

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c2 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #2 from Bruno Friedmann 2011-08-15 19:37:43 UTC --- Bjorn we agree that destroy totally boot with system V ? As mostly without -f I will loose chkconfig network off insserv: FATAL: service network has to be enabled to use service apache insserv: FATAL: service network has to be enabled to use service nfs insserv: FATAL: service network has to be enabled to use service smtp insserv: FATAL: service network has to be enabled to use service dnsmasq insserv: FATAL: service network has to be enabled to use service portmap insserv: FATAL: service network has to be enabled to use service smpppd insserv: FATAL: service network has to be enabled to use service libvirt-guests insserv: FATAL: service network has to be enabled to use service libvirtd insserv: FATAL: service network has to be enabled to use service avahi insserv: FATAL: service network has to be enabled to use service SuSEfirewall2_setup insserv: FATAL: service network has to be enabled to use service network-remotefs insserv: FATAL: service network has to be enabled to use service postgresql insserv: FATAL: service network has to be enabled to use service bacula-fd insserv: FATAL: service network has to be enabled to use service kerneloops insserv: FATAL: service network has to be enabled to use service mysql insserv: FATAL: service network has to be enabled to use service sshd insserv: FATAL: service network has to be enabled to use service fam insserv: exiting now! /sbin/insserv failed, exit code 1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:52

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c3 --- Comment #3 from Bjørn Lie 2011-08-15 21:52:53 CEST --- @ Bruno Sure :-) My bad, I wasn't aware that it's a goal to keep sysv as a possibility/fallback. I assumed we were going for full switch to systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:53

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c4 --- Comment #4 from Bruno Friedmann 2011-08-15 20:53:03 UTC --- @Borjn no pb, if we can drop sysv. Here's what I get whitout the full understanding (yet) of why. Once I boot with systemd, all stop during long time before I'm dropped to a tty. Then I realized dbus is not started at all. systemctl start dbus.service systemctl start NetworkManager.service systemctl start xdm.service and I get a Xorg running, and a 80% kde 4.7 running (some daemons like keyboard shortcuts etc seems to be killed somewhere ) But I've one service apache2 start refuse absolutely to start Find in attachement a output of all service installed here Was a fresh install of factory 12.1 when systemd was at release 28 or 30 I didn't tweak anything concerning systemd and just have ulimit raised in /etc/sysconfig/apache2 (but this is working at 100% with sysV ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:54

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c5 --- Comment #5 from Bruno Friedmann 2011-08-15 20:54:04 UTC --- Created an attachment (id=445865) --> (http://bugzilla.novell.com/attachment.cgi?id=445865) list of installed service files -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:56

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c6 --- Comment #6 from Bruno Friedmann 2011-08-15 20:56:24 UTC --- Created an attachment (id=445866) --> (http://bugzilla.novell.com/attachment.cgi?id=445866) Graph systemd The graph of the boot -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:57

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c7 --- Comment #7 from Bruno Friedmann 2011-08-15 20:57:21 UTC --- dmesg | grep systemd [ 0.000000] Command line: init=/bin/systemd root=/dev/vgsys/lvsuse keyboard=fr-ch-latin1 resume=/dev/vgsys/lvswap lang=fr_CH keytable=us splash=verbose verbose elevator=cfq rootfstype=ext4 rootflags=data=writeback video.allow_duplicates=1 file_caps=1 nomodeset nomodset blacklist=nouveau,radeon reboot=pci vga=0x34d [ 0.000000] Kernel command line: init=/bin/systemd root=/dev/vgsys/lvsuse keyboard=fr-ch-latin1 resume=/dev/vgsys/lvswap lang=fr_CH keytable=us splash=verbose verbose elevator=cfq rootfstype=ext4 rootflags=data=writeback video.allow_duplicates=1 file_caps=1 nomodeset nomodset blacklist=nouveau,radeon reboot=pci vga=0x34d [ 26.445817] systemd[1]: systemd 33 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse) [ 26.817224] systemd[1]: Set hostname to . [ 27.350760] systemd[1]: [/etc/init.d/postfix:12] Failed to add LSB Provides name sendmail.service, ignoring: File exists [ 27.545982] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 27.573333] systemd[1]: Found ordering cycle on NetworkManager.service/start [ 27.600177] systemd[1]: Walked on cycle path to syslog.target/start [ 27.626630] systemd[1]: Walked on cycle path to syslog.service/start [ 27.652494] systemd[1]: Walked on cycle path to network.target/start [ 27.677788] systemd[1]: Walked on cycle path to NetworkManager.service/start [ 27.677793] systemd[1]: Breaking ordering cycle by deleting job syslog.target/start [ 27.677814] systemd[1]: Found ordering cycle on basic.target/start [ 27.677818] systemd[1]: Walked on cycle path to sockets.target/start [ 27.677822] systemd[1]: Walked on cycle path to dbus.socket/start [ 27.677826] systemd[1]: Walked on cycle path to sysinit.target/start [ 27.677829] systemd[1]: Walked on cycle path to cycle.service/start [ 27.677832] systemd[1]: Walked on cycle path to localfs.service/start [ 27.677836] systemd[1]: Walked on cycle path to basic.target/start [ 27.677840] systemd[1]: Breaking ordering cycle by deleting job dbus.socket/start [ 27.677850] systemd[1]: Found ordering cycle on basic.target/start [ 27.677853] systemd[1]: Walked on cycle path to sysinit.target/start [ 27.677857] systemd[1]: Walked on cycle path to cycle.service/start [ 27.677861] systemd[1]: Walked on cycle path to localfs.service/start [ 27.677865] systemd[1]: Walked on cycle path to basic.target/start [ 27.677868] systemd[1]: Breaking ordering cycle by deleting job cycle.service/start [ 29.614050] systemd-fsck[572]: Root directory is writable, skipping check. [ 34.860754] systemd-fsck[900]: lvhome\xffffffc2\xffffffa0\xffffffa0: propre, 765823/37158912 fichiers, 56161077/148635648 blocs [ 35.094636] systemd-fsck[984]: lvsrv\xffffffc2\xffffffa0\xffffffa0: propre, 27483/4456448 fichiers, 7960529/17825792 blocs [ 36.552473] systemd-fsck[1112]: boot\xffffffc2\xffffffa0\xffffffa0: propre, 53/68272 fichiers, 98207/272372 blocs [ 54.446205] systemd[1]: network-remotefs.service: main process exited, code=exited, status=1 [ 356.225956] systemd[1]: apache2.service operation timed out. Terminating. [ 356.294531] systemd[1]: Unit apache2.service entered failed state. [ 356.380574] systemd[1]: Startup finished in 26s 628ms 933us (kernel) + 5min 29s 693ms 331us (userspace) = 5min 56s 322ms 264us. [ 443.855711] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 446.293184] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 479.285386] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 498.203261] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 507.382488] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 689.546560] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 702.735145] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 710.646325] dbus[3205]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details. [ 798.050036] systemd[1]: apache2.service operation timed out. Terminating. [ 798.112586] systemd[1]: Unit apache2.service entered failed state. [ 899.779611] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 942.076315] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 1094.203777] systemd[1]: rsyslog.service: main process exited, code=exited, status=1 [ 1094.231793] systemd[1]: Unit rsyslog.service entered failed state. [ 1216.007032] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16 Aug 16 Aug

08:29

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c8 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com --- Comment #8 from Andreas Jaeger 2011-08-16 08:29:25 UTC --- Same problem here - but only on my 32-bit system that uses NetworkManager. It works fine on my 64-bit x86-64 system without NetworkManager. Both run factory. I don't know what else is different that it only hits one of my systems. Disabling NetworkManager did not help. For me the cycle looks like: Found ordering cycle on basic.target/start Walked on cycle path to sockets.target/start Walked on... dbus.socket/start .. sysinit.target/start .. cycle.service/start .. localfs.service/start .. basic.target.start Breaking ordering cycle by deleting job dbus.socket/start Found ordering cycle on basic.target/start Walked on cycle path to sysinit.target/start .. cycle.service/start .. localfs.service/start .. basic.target.start Breaking ordering cycle by deleting job cycle.service/start -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:39

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c9 --- Comment #9 from Andreas Jaeger 2011-08-16 08:39:04 UTC --- I looked further at the loop and run: insserv -r boot.cycle This fixed the problem for me. Looking at the requires on my cycle, I'm not seeing the cycle :-( basic.target has: Requires=sysinit.target sockets.target After=sysinit.target sockets.target sysinit.target has: Wants=local-fs.target swap.target After=local-fs.target swap.target emergency.service emergency.target /etc/init.d/boot.cycle has # Required-Start: boot.localfs # Should-Start: boot.loadmodules The others have no dependency -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:44

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c10 --- Comment #10 from Andreas Jaeger 2011-08-16 08:44:08 UTC --- Created an attachment (id=445920) --> (http://bugzilla.novell.com/attachment.cgi?id=445920) /bin/systemd --test --system --log-level=debug output I have now a complete log file with the cycle in it - with boot.cycle enabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:45

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c11 --- Comment #11 from Andreas Jaeger 2011-08-16 08:45:21 UTC --- Created an attachment (id=445921) --> (http://bugzilla.novell.com/attachment.cgi?id=445921) /bin/systemd --test --system --log-level=debug output - after insserv -r boot.cycle The debug output after running insserv -r boot.cycle does not contain cycles and looks sane to me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:49

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c12 --- Comment #12 from Andreas Jaeger 2011-08-16 08:49:14 UTC --- # ls /etc/rc.d/rc3.d/S* /etc/rc.d/rc3.d/S01acpid /etc/rc.d/rc3.d/S04auditd /etc/rc.d/rc3.d/S08sshd /etc/rc.d/rc3.d/S01dbus /etc/rc.d/rc3.d/S04rpcbind /etc/rc.d/rc3.d/S09ntp /etc/rc.d/rc3.d/S01earlysyslog /etc/rc.d/rc3.d/S04splash_early /etc/rc.d/rc3.d/S10cups /etc/rc.d/rc3.d/S01fbset /etc/rc.d/rc3.d/S05nfs /etc/rc.d/rc3.d/S10nscd /etc/rc.d/rc3.d/S01microcode.ctl /etc/rc.d/rc3.d/S06cifs /etc/rc.d/rc3.d/S10postfix /etc/rc.d/rc3.d/S01purge-kernels /etc/rc.d/rc3.d/S07kbd /etc/rc.d/rc3.d/S10sbl /etc/rc.d/rc3.d/S01random /etc/rc.d/rc3.d/S08alsasound /etc/rc.d/rc3.d/S10smpppd /etc/rc.d/rc3.d/S01SuSEfirewall2_init /etc/rc.d/rc3.d/S08bluez-coldplug /etc/rc.d/rc3.d/S11cron /etc/rc.d/rc3.d/S02haldaemon /etc/rc.d/rc3.d/S08brld /etc/rc.d/rc3.d/S11smartd /etc/rc.d/rc3.d/S02network /etc/rc.d/rc3.d/S08network-remotefs /etc/rc.d/rc3.d/S12stoppreload /etc/rc.d/rc3.d/S03syslog /etc/rc.d/rc3.d/S08splash /etc/rc.d/rc3.d/S12SuSEfirewall2_setup -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:58

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c13 --- Comment #13 from Frederic Crozat 2011-08-16 11:58:47 UTC --- for the network part, we have two issues : - tell /etc/init.d/network to handle start NetworkManager when running under systemd (patch is done, pending review, I'll attach it) - enable NetworkManager systemd .service on both fresh install and upgrade (the upgrade part is tricky, due to the way OBS changes %release, ideas welcome) for the graphical interface not starting, it looks like bnc#707418 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:59

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c14 --- Comment #14 from Frederic Crozat 2011-08-16 11:59:43 UTC --- Created an attachment (id=445952) --> (http://bugzilla.novell.com/attachment.cgi?id=445952) don't start NM under systemd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:51

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c15 --- Comment #15 from Frederic Crozat 2011-08-16 14:51:46 UTC --- after more digging, cycles are caused by : - first cycle : syslog LSB service : we should probably replace it with rsyslog.service (which is disabled by default) - two other cycles : caused by /etc/insserv.conf parsing (which adds dependencies to current .services), more precisely $local_fs line. It shouldn't be a issue (since the two added dependencies are "ghost" entries) but it is causing the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:16

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c16 --- Comment #16 from Frederic Crozat 2011-08-16 17:16:42 UTC --- please test systemd from Base:System I just committed, it should fix localfs.service dependencies which were causing the various cycles. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17 Aug 17 Aug

07:58

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c17 --- Comment #17 from Andreas Jaeger 2011-08-17 07:58:22 UTC --- Thanks, the new systemd works for me. I pushed it to Factory now before more people run into it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:11

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c18 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdd@dodin.org --- Comment #18 from Frederic Crozat 2011-08-17 16:11:37 UTC --- *** Bug 712028 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=712028 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:40

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c19 --- Comment #19 from Dominique Leuenberger 2011-08-17 16:40:11 UTC --- (In reply to comment #16)

...

please test systemd from Base:System I just committed, it should fix localfs.service dependencies which were causing the various cycles.

Same for me: the systemd version from Base:system addresses my issue and X is getting started up properly again. Login and Network were no issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:02

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c20 --- Comment #20 from Bruno Friedmann 2011-08-17 20:02:50 UTC --- Same here, even without Base:System (I'm on factory) systemd now work with the given solution The only service that crash (didn't start) is apache2 To have it working I need to do cd /etc/init.d/ /apache2 start and then it goes up ??? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18 Aug 18 Aug

07:21

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c21 --- Comment #21 from Andreas Jaeger 2011-08-18 07:21:42 UTC --- Bruno, please file a separate bug for Apache. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:05

New subject: [Bug 712300] systemd: service startup order not blocking

https://bugzilla.novell.com/show_bug.cgi?id=712300 https://bugzilla.novell.com/show_bug.cgi?id=712300#c22 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #22 from Frederic Crozat 2011-08-18 10:05:09 UTC --- closing as fixed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

4642

Age (days ago)

4645

Last active (days ago)

List overview

Download

23 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 712300] New: systemd: service startup order not blocking

tags

participants (1)