The new "lirc_options.conf" is a very good improvement, especially for new init systems like systemd where passing options via command line is not very useful.
With the last update, which also brought this new feature, I had to reconfigure my system to work with the "UDP" driver, again.
I did so by changing the "driver" line to "udp" in "lirc_options.conf". After restarting lircd the log said, that port "/dev/lirc0" is not valid. I just commented this line in "lirc_options.conf" but this didn't do the trick. lircd still tries to open "/dev/lirc0" as UDP port. I had to search the web to find the default port and enter it manually to "lirc_options.conf".
Current behaviour: /dev/lirc0 is the default even if UDP driver is used
Expected behaviour: Just commenting the "device =" line should switch to the driver default so I don't have to manually set the default port.
Ack, this is not as it should and need to be fixed.
Duplicate of https://sourceforge.net/p/lirc/tickets/41/
which was closed, but somehow leaving 0.9.2 with the bug. (It has nothing to do with lirc_options.conf.)
Indeed, a regression. [tickets:#41] was closed using the old driver API, and the solution broke down when we merged the new API. This was anticipated, but this par twas never updated. Sigh.
Fix in [81b7b2]. This handles the not-set device argument as-is to the driver open() function. The default_open implementation (used by almost all drivers) falls back to the hardcoded driver default.
Leaving bug open for some time should there be more input.
Related
Tickets:
#41Commit: [81b7b2]
Last edit: Alec Leamas 2015-01-13
No more input, closing