search for: sem_open

...ohen (1): dahdi_get_auto_assigned_spans Shortlog of dahdi-tools changes since v2.9.0.1: Aslan Laoz (1): waitfor_xpds: handle the case of a failing AB Shaun Ruffell (2): hotplug: Check for auto_assign_spans only when ACTION is add. dahdi_cfg: error()->perror() when sem_open fails. Tzafrir Cohen (1): auto_assign_spans may be true even if not '1' The diffstat from the dahdi-linux v2.9.0 release: build_tools/install_firmware | 23 +++++ drivers/dahdi/dahdi-base.c | 12 ++- drivers/dahdi/firmware/Makefile | 191 +++++-----------------------...

...ohen (1): dahdi_get_auto_assigned_spans Shortlog of dahdi-tools changes since v2.9.0.1: Aslan Laoz (1): waitfor_xpds: handle the case of a failing AB Shaun Ruffell (2): hotplug: Check for auto_assign_spans only when ACTION is add. dahdi_cfg: error()->perror() when sem_open fails. Tzafrir Cohen (1): auto_assign_spans may be true even if not '1' The diffstat from the dahdi-linux v2.9.0 release: build_tools/install_firmware | 23 +++++ drivers/dahdi/dahdi-base.c | 12 ++- drivers/dahdi/firmware/Makefile | 191 +++++-----------------------...

...s: handle the case of a failing AB Oron Peled (2): hotplug: call handle_device.d/ actions for remove registration-order: Added dahdi_auto_assign_compat Shaun Ruffell (2): hotplug: Check for auto_assign_spans only when ACTION is add. dahdi_cfg: error()->perror() when sem_open fails. Tzafrir Cohen (1): auto_assign_spans may be true even if not '1' The diffstat from the dahdi-linux v2.9.0 release: build_tools/install_firmware | 23 +++++ drivers/dahdi/dahdi-base.c | 12 ++- drivers/dahdi/firmware/Makefile | 191 +++++-----------------------...

...s: handle the case of a failing AB Oron Peled (2): hotplug: call handle_device.d/ actions for remove registration-order: Added dahdi_auto_assign_compat Shaun Ruffell (2): hotplug: Check for auto_assign_spans only when ACTION is add. dahdi_cfg: error()->perror() when sem_open fails. Tzafrir Cohen (1): auto_assign_spans may be true even if not '1' The diffstat from the dahdi-linux v2.9.0 release: build_tools/install_firmware | 23 +++++ drivers/dahdi/dahdi-base.c | 12 ++- drivers/dahdi/firmware/Makefile | 191 +++++-----------------------...

...ohen (1): dahdi_get_auto_assigned_spans Shortlog of dahdi-tools changes since v2.9.0.1: Aslan Laoz (1): waitfor_xpds: handle the case of a failing AB Shaun Ruffell (2): hotplug: Check for auto_assign_spans only when ACTION is add. dahdi_cfg: error()->perror() when sem_open fails. Tzafrir Cohen (1): auto_assign_spans may be true even if not '1' Oron Peled (2): hotplug: call handle_device.d/ actions for remove registration-order: Added dahdi_auto_assign_compat The diffstat from the dahdi-linux v2.9.0 release: build_tools/install_firm...

...ohen (1): dahdi_get_auto_assigned_spans Shortlog of dahdi-tools changes since v2.9.0.1: Aslan Laoz (1): waitfor_xpds: handle the case of a failing AB Shaun Ruffell (2): hotplug: Check for auto_assign_spans only when ACTION is add. dahdi_cfg: error()->perror() when sem_open fails. Tzafrir Cohen (1): auto_assign_spans may be true even if not '1' Oron Peled (2): hotplug: call handle_device.d/ actions for remove registration-order: Added dahdi_auto_assign_compat The diffstat from the dahdi-linux v2.9.0 release: build_tools/install_firm...

Hello, Getting this error on dahdi_cfg. Reverting to 2.8 the error goes away: *line 15: Unable to create 'dahdi_cfg' mutex.* Is this a problem? Thanks in advance. Full detail: [ebox]> dahdi_cfg -vvvvvvv DAHDI Tools Version - 2.9.0.1 DAHDI Version: 2.9.0 Echo Canceller(s): HWEC Configuration ====================== SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2:

These three patches (for discussion only, NOT to be applied) implement a mutex system that lets the user limit the number of libguestfs instances that can be launched per host. There are two uses that I have identified for this: firstly so we can enable parallel-tests (the default in automake >= 1.13) without blowing up the host. Secondly oVirt has raised concerns about how to limit the