Bug#852127: qcontrold is not started on default

2017-09-17 Thread Hans Ulrich Elsner
On Mon, 23 Jan 2017 20:00:56 + Ian Campbell wrote: > On Mon, 2017-01-23 at 18:29 +, 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 d

Bug#852127: qcontrold is not started on default

2017-01-27 Thread Ian Campbell
On Wed, 2017-01-25 at 22:08 +, Thomas Pircher wrote: > On 2017-01-23 20:00, Ian Campbell wrote: > > [0] https://git.hellion.org.uk/?p=qcontrol.git;a=tree;f=systemd;h=f9b3c > > 358a84915b10bb780e0a8becdfa47604924;hb=HEAD > > Ok, I haven't managed to get the service files working. I copied the 

Bug#852127: qcontrold is not started on default

2017-01-25 Thread Thomas Pircher
On 2017-01-23 20:00, Ian Campbell wrote: [0] https://git.hellion.org.uk/?p=qcontrol.git;a=tree;f=systemd;h=f9b3c 358a84915b10bb780e0a8becdfa47604924;hb=HEAD Ok, I haven't managed to get the service files working. I copied the service and socket files to /usr/lib/systemd/user and enabled them w

Bug#852127: qcontrold is not started on default

2017-01-24 Thread Thomas Pircher
On 2017-01-23 20:00, Ian Campbell wrote: 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...). I'm by no means an expert with systemd, but I'll give it a go tonigh

Bug#852127: qcontrold is not started on default

2017-01-23 Thread Ian Campbell
On Mon, 2017-01-23 at 18:29 +, 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 fin

Bug#852127: qcontrold is not started on default

2017-01-23 Thread Thomas Pircher
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 sett

Bug#852127: qcontrold is not started on default

2017-01-21 Thread Thomas Pircher
Package: qcontrol Version: 0.5.5-2 Severity: normal Dear Maintainer, after an update from jessie to stretch the qcontrold daemon is no longer started. Both initscripts, qcontrold and qcontrol are in /etc/init.d but only the qcontrol script is linked from /etc/rc2.d. The latter script fails, as it