unconfigurable limits

Kay Sievers kay.sievers at vrfy.org
Mon Aug 16 16:47:11 PDT 2004


The hal-device-manager the python application using D-BUS is still
unusable, cause of the hard coded D-BUS limits.
Another limit reaching part of HAL simply removed D-BUS and
communicates now by its own domain socket, for that reason. 

What is the proper fix for that. After reading the list I only know,
what not to do.

Thanks,
Kay


  [kay at pim ~]$ hal-device-manager 
  Traceback (most recent call last):
    File "/usr/bin/hal-device-manager", line 15, in ?
      DeviceManager()
    File "/usr/share/hal/device-manager/DeviceManager.py", line 78, in __init__
      self.add_device_signal_recv (name);
    File "/usr/share/hal/device-manager/DeviceManager.py", line 94, in add_device_signal_recv
      udi)
    File "/usr/lib/python2.3/site-packages/dbus.py", line 89, in add_signal_receiver
      dbus_bindings.bus_add_match(self._connection, match_rule)
   File "dbus_bindings.pyx", line 1417, in dbus_bindings.bus_add_match
   dbus_bindings.DBusException: Connection ":1.10" is not allowed to add more match rules (incre
   ase limits in configuration file if required)



Btw: I've updated the "Get on the D-BUS" picture :)
  http://vrfy.org/projects/dbus/D-BUS-limit.jpg




More information about the dbus mailing list