Thomas Goirand <z...@debian.org> writes: > On 12/05/2014 03:04 AM, Gaudenz Steinlin wrote: >> OK I tested keystone on unstable now and this works as it should. It's >> definitely an improvement over the current unit file which does not work >> at all. > > Cool, thanks for your time! > >> One thing I noticed is that all services are disabled by default even >> though they were configured through debconf and should be ready to use. >> Is this intentional as an off by default behavior or is this a bug. How >> is this handled with sysvinit? >> >> Gaudenz > > This is a bug. With sysinit, it starts by default. What did you have to > do under systemd to make it start?
To make the services start on boot you have to manually enable them with systemctl enable *sercicename*. You can stil start them manually with systemctl start *servicename* and they work fine, even if they are disabled. I don't know why they are not enabled by default, but suspect it's because that's because you don't run dh_systemd_enable during the package build or something similar. Gaudenz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
