[dahdi-commits] dahdi/tools.git branch "master" updated.

[SVN commits to the DAHDI project]

branch "master" has been updated
       via  6ed0adc0869a4c6f37a30380ed96279498b1b151 (commit)
      from  5e75fa48f48d32eae8f037173ed94b8116fe1f21 (commit)

Summary of changes:
 dahdi_span_config |   11 +++++++++++
 1 file changed, 11 insertions(+)


- Log -----------------------------------------------------------------
commit 6ed0adc0869a4c6f37a30380ed96279498b1b151
Author: Shaun Ruffell <sruffell at digium.com>
Date:   Thu Dec 19 16:37:15 2013 -0600

    dahdi_span_config: Do not run auto span configuration if spans are auto assigned.
    
    I have seen cases were users run:
    
      # modprobe <driver>; dahdi_cfg -c <custom config file>
    
    and the spans end up misconfigured because dahdi_span_assignments ends up
    running, via udev, after the user configured the span the way it wanted.
    
    dahdi_span_assignments now looks at auto_assign_spans module parameter on
    dahdi.ko, like dahdi_handle_device already does, to determine if legacy or udev
    based configuration is being done.
    
    Signed-off-by: Shaun Ruffell <sruffell at digium.com>
    Acked-by: Oron Peled <oron.peled at xorcom.com>

diff --git a/dahdi_span_config b/dahdi_span_config
index 3562278..614c6a6 100755
--- a/dahdi_span_config
+++ b/dahdi_span_config
@@ -25,6 +25,17 @@ set -e
 
 #echo >&2 "$0($ACTION): DEBUG($# args): '$*'"
 
+# Old driver. These scripts probably won't work anyway.
+if [ ! -f /sys/module/dahdi/parameters/auto_assign_spans ]; then
+	$LOGGER "Old driver (no auto_assign_spans parameter). Skip $DEVPATH"
+	exit 0
+fi
+
+if [ $(cat /sys/module/dahdi/parameters/auto_assign_spans) -eq 1 ]; then
+	$LOGGER "auto_assign_spans=1. Skip $DEVPATH"
+	exit 0
+fi
+
 # Do we have a configuration?
 if [ -f /etc/dahdi/init.conf ]; then
 	. /etc/dahdi/init.conf

-----------------------------------------------------------------------


-- 
dahdi/tools.git