Bug#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)

[Ian Campbell]

On Wed, 2015-04-15 at 17:35 +0200, Michael Biebl wrote:
[...]
> > pkg-systemd-maintainers, see above: is there a way to wait for udev devices
> > to be available? What’s the current take on udev-settle, would that be a
> > reasonable workaround for this situation?
> 
> Possible solutions, in order of preference:

Thanks. I think the systemd unit files will be the right answer for
Stretch and beyond (and Jessie-backports) but I'm trying to find a
suitable workaround for Jessie, which currently uses the sysvinit
initscripts only.

Since Jessie is pretty much imminent I was hoping for a simple and
unobtrusive workaround which might get a freeze exception. I think most
of your suggestions would be too much at this stage, but thanks anyway.

> If I read the bug report correctly, qcontrol doesn't ship a native
> service file yet, though and only provides a SysV init script?

Yes, due to an oversight on my part when Michael S contributed the unit
files upstream :-/

> In that case, the (legacy) SysV init script could run "udevadm settle".
> This is super ugly though and not something I would recommend. I only
> mention it for completeness sake.

I think it's about the only plausible option for Jessie :-(

@reportbug (sorry I don't seem to know your real name), could you try
adding a call to "udev settle" to the qcontrold initscript, in the start
case right before the daemon is launched (I can be more specific if you
need).

Ian.