1. 16 Nov, 2015 1 commit
    • Tzafrir Cohen's avatar
      dahdi_cfg: -S has assumtions on system.conf order · cffc5158
      Tzafrir Cohen authored
      dahdi_cfg's -S (apply only to a specific span) uses the array chan2span
      to map channel numbers to span numbers.
      The problem is that it assumes that channels first appear in system.conf
      immediately after the span line of a specific span. Thus the following
      configuration breaks it:
      The best fix for that is to require -C to be used when -S is used (which
      is already the case in our udev hooks).
      Fixes DAHTOOL-69.
      Signed-off-by: 's avatarTzafrir Cohen <tzafrir.cohen@xorcom.com>
  2. 23 Jul, 2014 2 commits
  3. 09 Jul, 2014 1 commit
  4. 07 Jul, 2014 1 commit
  5. 12 Feb, 2014 1 commit
  6. 22 Jan, 2014 2 commits
    • Shaun Ruffell's avatar
      dahdi_cfg: Allow dynamic spans to handle udev based span assignment. · 69ce6f07
      Shaun Ruffell authored
      Prior to this commit, if auto_assign_spans was set to 0, it was possible to
      get in an endless loop creating and destroying spans. The primary reason was
      that all dynamic spans are destroyed and recreated each time dahdi_cfg runs, BUT
      dahdi_cfg was run each time a new span showed up in udev when auto_assign_spans
      was set to 0.
      Now dahdi_cfg will only destroy and recreate dynamic spans if dahdi_cfg is run
      without a specifc span number. Also, while creating dynamic spans, dahdi_cfg
      will pause for up to one second for the span to be assigned in order to ensure
      that the spans are numbered consistently when auto span assignment is
      Signed-off-by: 's avatarShaun Ruffell <sruffell@digium.com>
      Signed-off-by: 's avatarRuss Meyerriecks <rmeyerriecks@digium.com>
    • Shaun Ruffell's avatar
      dahdi_cfg: Add semaphore to prevent parallel execution. · 9989b877
      Shaun Ruffell authored
      When dahdi is configured for fully dynamic configuration on a device and
      span basis via sysfs and udev it is possible for multiple instances of
      dahdi_cfg to be run in parallel on different spans. If this happens it
      is possible to see errors on the console that tone zones are already
      registered since the check for the existence of a tone zone and the
      re-registering needs to be atomic.
      dahdi_cfg will now prevent itself from running in parallel.
      Signed-off-by: 's avatarShaun Ruffell <sruffell@digium.com>
      Signed-off-by: 's avatarRuss Meyerriecks <rmeyerriecks@digium.com>
  7. 12 Dec, 2013 1 commit
  8. 08 Oct, 2013 1 commit
  9. 28 May, 2013 1 commit
  10. 02 Nov, 2011 2 commits
  11. 20 Sep, 2010 1 commit
  12. 18 Aug, 2010 1 commit