Hi Stefan,
> In my experience, with several USB/ hotpluggable lirc devices and a
> separate /var/ partition, this is the actual problem. What happens is
> that the lircd socket gets created underneath the final /var/run/,
> /run/ respectively, before it is mounted on its final place, thereby
>
Hi Stefan,
> I'm pretty sure this is due to a missing LSB dependency on $local_fs
> for lirc's init script.
I'm not so sure this is really the case: The problem is really that the
udev rule triggers a lirc (re)start too soon on the boot sequence, not
that the normal init script invocation is too
Hi
On Wednesday 06 June 2012, Matthijs Kooijman wrote:
> Hi Stefan,
>
> > I'm pretty sure this is due to a missing LSB dependency on $local_fs
> > for lirc's init script.
> I'm not so sure this is really the case: The problem is really that the
> udev rule triggers a lirc (re)start too soon on t
tags 676343 + pending
thanks
Hi
On Wednesday 06 June 2012, Matthijs Kooijman wrote:
[…]
> I was trying to get lirc running, but for some reason the /var/run/lirc
> directory showed up empty after boot. Lircd was running, but the socket
> and pidfile were not there. After a morning of debugging I
Package: lirc
Version: 0.9.0~pre1-1
Severity: normal
Hi,
I was trying to get lirc running, but for some reason the /var/run/lirc
directory showed up empty after boot. Lircd was running, but the socket
and pidfile were not there. After a morning of debugging I found out
what was happening, but I'm
5 matches
Mail list logo
