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. To double check that I'm not just making this up, can you send the output of sh -x /etc/init.d//lirc start, so that I can be sure that it really is starting without a --device line? Thanks, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | ----------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
