Splitting the NIS package is difficult due in part to some minor licensing problems which prevent the package going through new in Debian. There are also some entertaining issues with handling upgrades if the init script is split due to init scripts being conffiles, although nothing insurmountable. The main reason that most distributions do this is actually that the Debian/Ubuntu NIS packages combine code released as three different tarballs for upstream.
The current default is going to be sensible for the majority of systems (setting up a new domain is a relatively uncommon operation) and I would much rather move towards making the client install less manual rather than more so. Please report the problem with starting up with NISCLIENT=false as a separate issue, including the output produced by the init script as it runs. That sounds like it shouldn't be happening. ** Summary changed: - nis service slow to start up on server + Delay during installation of master server -- Delay during installation of master server https://bugs.launchpad.net/bugs/138436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
