Comment 22 for bug 50430

Dag-Erling: The point here is that the Network Manager integration in NIS (which is disabled by default) is supposed to work around these issues by doing something very similar to what the script fragment you posted does. This means that NIS is affected by only a subset of the problems that affect the system in general - usually only those where Network Manager reports a connection status that does not correspond to reality.

Without something like that there is a general issue many services have with Network Manager independently of any bugs in Network Manager.

Johan: It mostly eliminates the problem that causes 90% of these issues but unfortunately it doesn't tell us what went wrong.

Could one or both of you please insert something into the bind wait loop in /etc/init.d/nis to log the output of nm-tool while it is probing (eg:

               for i in 1 2 3 4 5 6 7 8 9 10
                do
                        /usr/bin/nm-tool >> /tmp/nm-tool-log # ADDED LINE
                        sleep 1
                        log_action_cont_msg "."

) and then also log the output of nm-tool when you are able to restart NIS succesfully. If Network Manager is reporting bad information this should confirm it; it may also show that NIS is paying attention to the wrong information from Network Manager.