Strange behaviour with multiple lircd and -l option

[Tino K. <tin...@ti...>]

Hi folks,

I try to achieve the following scenario:

- lircd(1) starts with the -l option and also receives events from
  remote(1)

- lircd(2) starts, connects to lircd(1) and receives events from
  remote(2)

- lirc clients start and receive events from both remotes

- I restart lircd(2) at suspend/resume, because the remote sensor is
  part of a DVB-T USB box that doesn't survive suspend/resume and I
  have to reload its driver

- lircd(1) is running all the time, lirc clients won't notice that
  lircd(2) was restarted

However, I get the following behaviour:

- I restart lircd(2), lircd(1) closes it's socket and clients don't
  receive anyting anymore

lircd(2):

lircd-0.8.0[18397]: caught signal
lircd-0.8.0[18397]: closing '/dev/input/by-id2/0ccd-0038'

lircd(1):

lircd-0.8.0[18395]: removed client
lircd-0.8.0[18395]: closing '/dev/input/by-id2/05ac-8240'

irw:
connect: Connection refused


- I have to restart lircd(1) and all clients to get everything working
  again

Is it a bug that lircd(1) closes it's input device
(/dev/input/by-id2/05ac-8240) and communication socket /dev/lircd) when
lircd(2) disconnects? Or just a design flaw that can not be fixed?

Regards,
Tino