On Thu, 2015-04-16 at 10:28 +0200, reportbug wrote:
On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote:
@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
On Thu, Apr 16, 2015 at 10:36:32 +0100, Ian Campbell wrote:
On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote:
But I did have one occasion where one out of my 3 qnaps repeatedly failed
to
boot after the latest kernel update (or at least the latest flash-kernel
trigger, maybe it was
On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote:
@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).
Hi. It pains
On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote:
On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote:
BTW, when this fails the system still booted and you could login and fix
it, i.e. it didn't stall the boot or anything, is that right? If that is
the case a release note might be
On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote:
BTW, when this fails the system still booted and you could login and fix
it, i.e. it didn't stall the boot or anything, is that right? If that is
the case a release note might be the most plausible action at this
point.
When I saw
Hi,
Am 14.04.2015 um 21:56 schrieb Michael Stapelberg:
On Tue, Apr 14, 2015 at 8:59 PM, Ian Campbell i...@debian.org wrote:
On Tue, 2015-04-14 at 10:02 +0200, Michael Stapelberg wrote:
Apr 02 12:08:28 hostname systemd[1]: Started LSB: Start
qcontrol daemon.
This line in
[+cc pkg-systemd-maintainers]
On Tue, Apr 14, 2015 at 8:59 PM, Ian Campbell i...@debian.org wrote:
On Tue, 2015-04-14 at 10:02 +0200, Michael Stapelberg wrote:
Apr 02 12:08:28 hostname systemd[1]: Started LSB: Start
qcontrol daemon.
This line in the logfile indicates