Indeed. What I've found is that the user add function to bring the user/group "nsd" into existence comes AFTER (WTF?!?!) the system tries to start the daemon. What I tried doing was using another unprivileged user (e.g. daemon) so the daemon starts when I do the "dpkg --configure -a" or "apt-get -f install". I do not want to do a random "useradd"; I would rather the packaging system add it per policy, not assign a normal user ID (anything above 1000) willy-nilly.
I'll show you an example which can tacked on at the end of the /etc/nsd/nsd/conf file: server: username: "daemon" Then I perform a "dpkg --configure -a" or "apt-get -f install" Once the program starts, I will shut it down via "service nsd stop" , then removing the above stanza from /etc/nsd/nsd.conf. Then it works normally since the useradd portion of the script had a chance to do its thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311886 Title: nsd fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1311886/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
