Hello Uwe, * Uwe Kleine-König <uklei...@debian.org> [231107 22:06]: > on installation of pdns-server the pdns.service is automatically > started. However in my case port 53 is already bound and so it fails to > start. (That might also happen if port 53 isn't blocked because the > default config isn't suitable to successfully run pdns? I didn't check.) > [..] > to the journal. If you don't notice this immediately and stop the > service this effectively spams your journal in a very short time. > > IMHO the above mentioned settings are not suitable as a default for a > distribution's package even if the default configuration worked. It > should be an administrator's choice to configure such a behaviour.
I respectfully disagree. If users have pdns-server installed and running, they want it restarted ASAP. This is the correct behaviour. Now, I believe Debian's default of "start various daemons on install" is just wrong nowadays. For a long time there was nothing we could do in pdns-server (and pdns-recursor) to change this without breaking existing installs, but I'll think about passing --no-enable to dh_installsystemd. I think this should be safe for upgrades, and new installs then need to systemctl enable pdns-server.service explicitly. Chris
