On Mon, 23 Jan 2017 20:00:56 +0000 Ian Campbell <i...@debian.org> wrote: > On Mon, 2017-01-23 at 18:29 +0000, Thomas Pircher wrote: > > Thomas Pircher wrote: > > > after an update from jessie to stretch the qcontrold daemon is no > > > longer > > > started. > > > > This should have read "is no longer enabled by default". > > I can start the qcontrold manually and the daemon works fine, once it > > is > > started. > > > > I have worked around this issue by manually setting the link in > > /etc/rc2.d/Sxxqcontrold. Is there maybe something I'm missing after > > the switch to systemd? > > qcontrold should be started by something in rcS.d rather than rc2.d. Or > at least it is/was on sysvinit, perhaps something has changed WRT > systemd or systemd's LSB integration? > > Upstream has socket and service files included, see [0]. Perhaps > qcontrol should be switched over. I can't remember why I didn't, > perhaps just "if it ain't broke" (except now it is...). > > Do you know much about systemd, perhaps you could try dropping those > files into the appropriate place and see if it helps? If not I will try > and make some time soon. >
I ran into the same issue today and solved it by changing the start run levels in /etc/init.d/qcontrold to # Default-Start: 2 3 4 5 Trying to enable the service with Default-Start: S always gave me an error message by systemctl. With the new run levels it works fine on Stretch. —HU
