Control: tags -1 moreinfo On Tue, 21 Oct 2014 09:00:26 -0400 Sam Hartman <[email protected]> wrote: > package: debhelper > version: 9.20141003 > severity: wishlist > > I suspect a lot of folks will be writing systemd service units in the > future. > While writing units for krb5-kdc, I ran across an issue. > > On first install, until you set up your database, it's kind of expected > that krb5-kdc will fail to start. > Systemd is a lot more careful about noticing this than sysvinit, and > gives significantly less flexibility for hiding the error. > > I'd really like to say that errors starting krb5-kdc on install or > upgrade should not break the installation run, but errors stopping it in > prerm should. > > I can do that using the --error-handler parameter to dh_installinit. > That means I need to actually create an error handler in my prerm and > postinst. > I think this situation is going to be common enough that I want such an > error handler available with a command line option to dh_installinit. > > Or perhaps we should decide that ignoring stop errors on upgrade or > uninstall is OK and I can just do --error-handler=true? > > Thoughts welcome. > > --Sam > >
Hi Sam, Thanks for the bug report. It sounds like you rather want krb5-kdc not to start on initial installation. This is doable via the --no-start (possibly combined with --no-enable). Note: I do not remember if both these options were available in 2014 when you filed this bug. Do you feel that approach handles your particular issue? Thanks, ~Niels
