Mailinglist Archive: opensuse-factory (551 mails)

< Previous Next >
Re: [opensuse-factory] Systemd by default
On 05/30/2011 10:29 AM, Frederic Crozat wrote:
Le dimanche 29 mai 2011 à 09:55 +0200, Tim a écrit :
Hi,

to my knowledge systemd supposed to be the default init daemon in 12.1.
Doesn't it make sense to activate it now (or as early as possible) to
get at least some feedback from the people running factory?

Damn, you're cutting all the surprise effect ;)

I was planning to announce I'll be working full-time for June month,
starting next week, on systemd integration in Factory.

Of course, feedback from people running Factory and help from packagers
will be extremely useful, to get the best possible experience in 12.1
for systemd.

More on this next week ;)


My actual result ( tested 15 minutes ago ) are quite bad.
with systemd system-sysinit and networkmanager activated I just get no network
kde refuse to start due to dbus error and a lot of others services.

cat /var/log/messages | grep -i systemd
May 30 10:38:11 c-3po kernel: [ 27.616858] systemd[1]: systemd 26 running in
system mode. (+PAM +LIBWRAP +AUDIT +SELINUX
+SYSVINIT +LIBCRYPTSETUP; suse)
May 30 10:38:11 c-3po kernel: [ 27.659579] systemd[1]: Set hostname to
<c-3po.vellerat.ioda.net>.
May 30 10:38:11 c-3po kernel: [ 28.413789] systemd[1]:
[/etc/init.d/postfix:12] Failed to add LSB Provides name
sendmail.service, ignoring: File exists
May 30 10:38:11 c-3po kernel: [ 28.462158] systemd[1]: Found ordering cycle
on basic.target/start
May 30 10:38:11 c-3po kernel: [ 28.462164] systemd[1]: Walked on cycle path
to sockets.target/start
May 30 10:38:11 c-3po kernel: [ 28.462169] systemd[1]: Walked on cycle path
to dbus.socket/start
May 30 10:38:11 c-3po kernel: [ 28.462173] systemd[1]: Walked on cycle path
to sysinit.target/start
May 30 10:38:11 c-3po kernel: [ 28.462177] systemd[1]: Walked on cycle path
to sysstat.service/start
May 30 10:38:11 c-3po kernel: [ 28.462182] systemd[1]: Walked on cycle path
to remote-fs.target/start
May 30 10:38:11 c-3po kernel: [ 28.462186] systemd[1]: Walked on cycle path
to network.target/start
May 30 10:38:11 c-3po kernel: [ 28.462190] systemd[1]: Walked on cycle path
to network.service/start
May 30 10:38:11 c-3po kernel: [ 28.462194] systemd[1]: Walked on cycle path
to SuSEfirewall2_init.service/start
May 30 10:38:11 c-3po kernel: [ 28.462198] systemd[1]: Walked on cycle path
to basic.target/start
May 30 10:38:11 c-3po kernel: [ 28.462203] systemd[1]: Breaking ordering
cycle by deleting job dbus.socket/start
May 30 10:38:11 c-3po kernel: [ 28.462218] systemd[1]: Found ordering cycle
on basic.target/start
May 30 10:38:11 c-3po kernel: [ 28.462222] systemd[1]: Walked on cycle path
to sysinit.target/start
May 30 10:38:11 c-3po kernel: [ 28.462226] systemd[1]: Walked on cycle path
to sysstat.service/start
May 30 10:38:11 c-3po kernel: [ 28.462230] systemd[1]: Walked on cycle path
to remote-fs.target/start
May 30 10:38:11 c-3po kernel: [ 28.462234] systemd[1]: Walked on cycle path
to network.target/start
May 30 10:38:11 c-3po kernel: [ 28.462239] systemd[1]: Walked on cycle path
to network.service/start
May 30 10:38:11 c-3po kernel: [ 28.462243] systemd[1]: Walked on cycle path
to SuSEfirewall2_init.service/start
May 30 10:38:11 c-3po kernel: [ 28.462247] systemd[1]: Walked on cycle path
to basic.target/start
May 30 10:38:11 c-3po kernel: [ 28.462252] systemd[1]: Breaking ordering
cycle by deleting job sysstat.service/start
May 30 10:38:11 c-3po kernel: [ 28.462278] systemd[1]: Found ordering cycle
on basic.target/start
May 30 10:38:11 c-3po kernel: [ 28.462283] systemd[1]: Walked on cycle path
to sysinit.target/start
May 30 10:38:11 c-3po kernel: [ 28.462287] systemd[1]: Walked on cycle path
to cpufreq.service/start
May 30 10:38:11 c-3po kernel: [ 28.462291] systemd[1]: Walked on cycle path
to basic.target/start
May 30 10:38:11 c-3po kernel: [ 28.462295] systemd[1]: Breaking ordering
cycle by deleting job cpufreq.service/start
May 30 10:38:11 c-3po kernel: [ 29.572210] systemd-fsck[530]: Root directory
is writable, skipping check.
May 30 10:38:11 c-3po kernel: [ 31.054692] systemd-fsck[741]: srv : propre,
29329/6553600 fichiers, 8240453/26214400 blocs
May 30 10:38:11 c-3po kernel: [ 31.055490] systemd-fsck[747]: home : propre,
738766/16777216 fichiers, 51330223/67108864 blocs
May 30 10:38:11 c-3po kernel: [ 32.223395] systemd-cryptsetup[855]:
Encountered unknown /etc/crypttab option 'none', ignoring.
May 30 10:38:11 c-3po kernel: [ 32.224951] systemd-cryptsetup[855]: Volume
cr_sda2 already active.
May 30 10:38:11 c-3po kernel: [ 32.281183] systemd-fsck[864]: boot : propre,
63/66264 fichiers, 104813/264192 blocs
May 30 10:38:11 c-3po kernel: [ 38.410953] systemd[1]: network.service:
control process exited, code=exited status=2
May 30 10:38:11 c-3po kernel: [ 38.411091] systemd[1]: Unit network.service
entered failed state.
May 30 10:38:12 c-3po kernel: [ 39.604429] systemd[1]: nscd.service: control
process exited, code=exited status=7
May 30 10:38:12 c-3po kernel: [ 39.604438] systemd[1]: Unit nscd.service
entered failed state.
May 30 10:38:55 c-3po kernel: [ 83.208881] systemd[1]: network.service:
control process exited, code=exited status=2
May 30 10:38:55 c-3po systemd[1]: Unit network.service entered failed state.
May 30 10:39:15 c-3po kernel: [ 102.540229] systemd[1]: postgresql.service:
control process exited, code=exited status=1
May 30 10:39:15 c-3po kernel: [ 102.548159] systemd[1]: Unit
postgresql.service entered failed state.
May 30 10:41:41 c-3po systemd[1]: Reloading.
May 30 10:41:42 c-3po systemd[1]: [/etc/init.d/postfix:12] Failed to add LSB
Provides name sendmail.service, ignoring: File exists
May 30 10:43:33 c-3po systemd[1]: dbus.service: main process exited,
code=exited, status=1
May 30 10:43:33 c-3po kernel: [ 360.961086] systemd[1]: Unit dbus.service
entered failed state.
May 30 10:46:42 c-3po systemd[1]: apache2.service operation timed out.
Terminating.
May 30 10:46:42 c-3po kernel: [ 549.329395] systemd[1]: kbd.service operation
timed out. Terminating.
May 30 10:46:42 c-3po kernel: [ 549.348341] systemd[1]: Unit kbd.service
entered failed state.
May 30 10:46:42 c-3po kernel: [ 549.354371] systemd[1]: Unit apache2.service
entered failed state.
May 30 10:46:42 c-3po systemd[1]: Startup finished in 27s 675ms 424us (kernel)
+ 8min 41s 768ms 674us (userspace) = 9min 9s
444ms 98us.
May 30 10:49:11 c-3po systemd-initctl[11103]: Got request for unknown runlevel
u, ignoring.
May 30 10:49:26 c-3po systemd-fsck[11135]: Root directory is writable, skipping
check.
May 30 10:49:30 c-3po systemd-initctl[11232]: Received environment initctl
request. This is not implemented in systemd.
May 30 10:49:30 c-3po systemd[1]: Found ordering cycle on sysinit.target/start
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to sysstat.service/start
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to remote-fs.target/stop
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to network.target/stop
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to network.service/stop
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to
SuSEfirewall2_init.service/stop
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to basic.target/start
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to sockets.target/start
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to dbus.socket/start
May 30 10:49:30 c-3po systemd[1]: Walked on cycle path to sysinit.target/start
May 30 10:49:30 c-3po systemd[1]: Breaking ordering cycle by deleting job
sysstat.service/start
May 30 10:49:30 c-3po kernel: [ 717.356990] systemd[1]: Found ordering cycle
on sysinit.target/start
May 30 10:49:30 c-3po kernel: [ 717.357017] systemd[1]: Walked on cycle path
to cpufreq.service/start
May 30 10:49:30 c-3po kernel: [ 717.357025] systemd[1]: Walked on cycle path
to basic.target/start
May 30 10:49:30 c-3po kernel: [ 717.357032] systemd[1]: Walked on cycle path
to sockets.target/start
May 30 10:49:30 c-3po kernel: [ 717.357038] systemd[1]: Walked on cycle path
to dbus.socket/start
May 30 10:49:30 c-3po kernel: [ 717.357044] systemd[1]: Walked on cycle path
to sysinit.target/start
May 30 10:49:30 c-3po kernel: [ 717.357050] systemd[1]: Breaking ordering
cycle by deleting job cpufreq.service/start
May 30 10:49:30 c-3po kernel: [ 717.666527] systemd[1]: sshd.service: main
process exited, code=exited, status=255
May 30 10:49:30 c-3po kernel: [ 717.819091] systemd[1]: Unit sshd.service
entered failed state.


mainly everything coming from that kind of
ay 30 10:38:11 c-3po kernel: [ 38.465793] NetworkManager[1137]: <error>
[1306744691.184409] [nm-dbus-manager.c:278]
nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the
message bus daemon is running! Message: Failed to
connect to socket /var/run/dbus/system_bus_socket: No such file or directory

I know my factory is a constant rolling release started last year in september.

Kay, Frederic should we open a king of meta-bug for systemd that we let open
until we success it's integration ?


--

Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
References