Comment 2 for bug 740777

Egon, thanks for the bug report.

Can you explain what is not working correctly when samba comes up early?

It shouldn't cause any problems for samba to begin listening without any network interfaces, unless you bind it to a specific IP address. When you do that, you need to customize the init script to wait for that interface to come up anyway.

Absent that answer though, I do think that there's no real benefit to having smbd up before the network. It would probably be better to just do 'start on runlevel [2345] or net-device-up IFACE!=lo'. This will make sure that its started back up when moving from runlevel 1 -> 2, and will make sure its started any time a network device is configured and its not running.

I'm going to mark the bug as Triaged, and lower the importance to Low. If there are real, adverse affects caused by the early start, we can raise the importance once they are documented here.