Greetings again-
Thanks for the reply:
> 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.
OK, that sounds good.
My complaint about the installation script seems to be due to this boilerplate
in /var/lib/dpkg/info/pdnsd.postinst:
# Automatically added by dh_installinit
if [ -x "/etc/init.d/pdnsd" ]; then
update-rc.d pdnsd defaults >/dev/null
if [ -x "`which invoke-rc.d 2>/dev/null`" ]; then
invoke-rc.d pdnsd start || exit $?
else
/etc/init.d/pdnsd start || exit $?
fi
fi
# End automatically added section
This boilerplate shows the standard for debian to start the init.d script even
if unconfigured. Maybe a line in /etc/default/pdnsd could say
"ENABLE_PDNSD=false"
and then check for that in the /etc/init.d/pdnsd script to issue the message:
"Please configure IP address and nameservers in /etc/pdnsd.conf then change
ENABLE
to true" for example.
-Captain
