On Sat, 11 Nov 2006 21:47:53 +0100, Stephen Gran <[EMAIL PROTECTED]> wrote:
This one time, at band camp, Rafał Rutkowski said:
When the daemon is started by init.d/lirc script, it quits when a client
(tested with mplayer and KDE lirc) tries to connect. It leaves the
following messages in the syslog:
Oct 22 15:26:34 rudy lircd-0.8.0[5594]: could not get file information
for UNCONFIGURED
Oct 22 15:26:34 rudy lircd-0.8.0[5594]: default_init(): No such file or
directory
This is the hint - it should be looking at /dev/lirc0, not UNCONFIGURED.
However, if the daemon is started manually by invoking
lircd --device=/dev/lirc0
(as root), everything works fine.
This is because you haven't yet configured lircd.conf or hardware.conf.
It is arguably a flaw in lirc that it will start without knowing what
hardware to talk to, but it's a design flaw, rather than a bug.
That's it. A line
DEVICE="UNCONFIGURED"
appeared in the hardware.conf file after the update. I don't know how I
could have missed it. It wasn't there before the 0.8 version, that's for
sure. Removing the line makes the init script use the /dev/lirc0 device
and solves the problem. And the problem was obviously no bug :)
Thank you for your time
--
Rafał Rutkowski
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
