Quoting Michael Biebl (bi...@debian.org): Thanks for your answer, Michael,
> Imho, a the correct way to fix this, is to fix samba to make it listen > for network changes (via netlink). Hmmm, imho a bit invasive and not sure that samba developers want this. > > There is another hack (which of course I don't recommend to be added to > the samba Debian package): > > Change /etc/init.d/samba and add a call to "nm-online" before you start > the samba daemons. > This tool will exit as soon as NetworkManager has established a network > connection. It will exit after a 30 second timeout, if no connection > could be established during that time. So your boot won't block > indefinitely. Yeah, that's an interesting hack but it should be kept up to the local admin. I don't think it's worth including it in samba packages and add a 30s timeout delay to each samba server boot sequence... > To sum up: I don't plan to add Provides: $network to the NM init > script, for the given reasons. > Also, $network is a virtual facility, which I can't simply modify by > adding a "Provides: $network" to the LSB header, as insserv doesn't > allow that. I was thinking more or less the same but couldn't answer that in the name of n-m maitnainers. > > So, I'm not sure what to do about this bug in network-manager. If it > should be re-assigned/closed/... Either close or mark "wontfix", I would say.
signature.asc
Description: Digital signature
