https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c1 Lars Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #1 from Lars Müller 2011-12-09 18:22:44 CET --- Either this is an issue with systemd - adding Frederic to get his input on this - or we have to provide 'native' systemd files for the services Samba offers. We have them already upstream and need to check and merge them to our packages. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c3 Agnelo de la Crotche changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hippolyte@shaw.ca --- Comment #3 from Agnelo de la Crotche 2011-12-13 16:10:36 UTC --- Different poster but same machines ... Increasing WAIT_FOR_INTERFACES from 30 to 300 didn't help. In the meantime we experienced the same issue on another machine (64bit, 2 netcards). On the 3 machines, nmb seems to be the bottleneck in systemd: - it takes about 5 minutes for the login prompt to appear. - only the first netcard gets an IP allocated. - However nmb is successfully started. - the value of WAIT_FOR_INTERFACES doesn't affect the boot time. No matter how long it waits for netcards, it takes about 5 minutes to boot - which I guess is the timeout for services in systemd. When nmb is off in systemd: - it boots normally - all netcards get their IP. Thus it is a lot faster to disable nmb at boot and start it manually. I haven't tested nmb on a machine with a single netcard. So I don't know if the problem is nmb itself or the combination of nmb with several netcards. In system V, everything is ok. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c5 --- Comment #5 from Agnelo de la Crotche 2011-12-13 17:26:00 UTC --- That worked. - Boot is (a lot) faster. - WAIT_FOR_INTERFACES is back to default (30) - All interfaces get an IP. - smb and nmb are started. - samba server is working. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c7 --- Comment #7 from Agnelo de la Crotche 2011-12-13 19:17:40 UTC --- Created an attachment (id=467289) --> (http://bugzilla.novell.com/attachment.cgi?id=467289) disables rcnmb start causing systemd to hang for 5 minutes. Commenting out this line allows systemd to boot normally, while all network interfaces get an ip and nmb starts successfully. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c9 --- Comment #9 from Frederic Crozat 2011-12-14 09:49:56 UTC --- could you try replacing the offending line with systemctl restart --ignore-dependencies nmb.service when booting 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.

https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c11 --- Comment #11 from Frederic Crozat 2011-12-14 12:50:30 UTC --- I didn't saw ANY data corruption report related with systemd (and this is off topic to this bug report). Bobby, could you do similar test (replace rcnmb start with systemctl restart --ignore-dependencies nmb.service) ? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c13 --- Comment #13 from Agnelo de la Crotche 2011-12-15 14:00:24 UTC --- (In reply to comment #12)

Agnelo, do you have a link to the place where you read about data corruption?

In the network subforum of the openSUSE forum (a sticky post at the top of the page). The site is down since yesterday. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735943 https://bugzilla.novell.com/show_bug.cgi?id=735943#c15 --- Comment #15 from Marius Tomaschewski 2012-01-10 13:04:28 UTC --- (In reply to comment #12)

(In reply to comment #11)

...

I didn't saw ANY data corruption report related with systemd (and this is off topic to this bug report).

I've no idea how this is related, but bnc#732910 reports overwritten dhclient-script -- the reporter says, it happens only while a systemd boot.

FYI: It was a bug in dhclient (in a patch), stderr -> /dev/null were marked close-on-exit and thus has been closed while exec of dhclient-script. So a completely unrelated 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.