Comment 11 for bug 138436

Just to clarify wrt NISCLIENT=false: the init script will wait for up to ten seconds for the client to bind to a server but otherwise it shouldn't wait for anything so if NISCLIENT=false the startup should be fairly quick. The only thing that jumps out at me is that if you are running a slave and have specified the master in /etc/default/nis it will attempt to sync the maps from the master server when it starts which could take a while to time out if the master is unavailaible. Without more information about the lengths of the delays or where in the process they occur it's difficult to comment further. In any case, it's a separate issue to the default configuration being for a NIS client.