On Tue, Oct 17, 2006 at 11:38:00AM -0700, captain toro wrote: > The reason pdnsd does not start when the init.d script is called by the > install > script is shown to be the named already using port 53. That is the correct > behavior. > The pdnsd.conf file needs to be customized before the pdnsd can run anyway.
> The install script should not fail because pdnsd does not start. That is the > incorrect behavior. I don't agree. If the primary use of the package is to run a daemon, and the daemon fails to start for *any* reason, it's better to leave the package in an unconfigured state so that the admin can address this by hand. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
