From: <li...@ba...> - 2008-08-19 20:22:25
|
Hi! Bastien Nocera "ha...@ha..." wrote: > On Mon, 2008-08-18 at 15:07 -0400, Matthew Bodkin wrote: >>>>>> Would it help if lircd does not close the device once it has been >>>>>> opened? >>>> >>>>> Not really, there's no device when we start up the application. >>>> >>>> In the use case that you have posted it would make a difference. Once >>>> opened, lircd would never close the device. >>>> Currently, if you unplug the receiver while there is a client connected, >>>> lircd will retry opening the device until it is available again. >>> >>> Well, it would help, but it would still exit when we try to connect and >>> the device is gone. >>> >>> The main problem is that lircd exits at all. I don't mind how it fails. >>> The problem is that there's cases where the user has setup everything >>> properly, and lircd could be not running. The user has no way to restart >>> lircd without using either the command-line, or setting up the receiver >>> again in gnome-lirc-properties. And that's not what we want to see. >> >> If it makes any difference, I second the call to always keep lircd >> running and maintaining clients connections regardless of connected >> hardware or LIRC reloads. > Client connections being kept alive isn't such a problem for my use > case, but I certainly need lircd to be kept running... Currently lircd will exit if the device is not available and the 1st client connects. If a client already is connected and the device becomes unavailable, the 2nd client will be able to connect without any problem. This is kind of inconsistent and I would propose to change the code that the 1st client will be able connect regardless whether the device can be opened or not. Christoph |