expert mode

README.md

@@ -80,7 +80,7 @@ Start the configuration script:
 
 There are only a few things that need to be specified, most importantly, the reflector callsign and the IP addresses for the IPv4 and IPv6 listen ports and a transcoder port, if there is a transcoder. Dual-stack operation is enabled by specifying both an IPv4 and IPv6 address. It's even possible to operate in an IPv6-only configuration by leaving the IPv4 address to the default `none`. Obviously the transcoder is only specified for an XLX reflector. If you are building an XLX system with a transcoder, you can also specify which channels get transcoder support. There are also true/false flags to prevent G3 support and so that you can build executables that will support gdb debugging.
 
-Be sure to write out the configuration files and look over the up to 5 different configration files that are created. The first file, reflector.cfg is the memory file for rconfig so that if you start that script again, it will remember how you left things. There are one or two `.h` files for the reflector and ambed and there are one or two `.mk` files for the reflector and ambed makefiles. You should **not** modify these files by hand unless you really know exactly how they work. The rconfig will not start if it detects that an XLX or XRF server is already running. If you do change the configuration after you have compiled the code, it is safest if you clean the repo and then recompile.
+Be sure to write out the configuration files and look over the up to 5 different configration files that are created. The first file, reflector.cfg is the memory file for rconfig so that if you start that script again, it will remember how you left things. There are one or two `.h` files for the reflector and ambed and there are one or two `.mk` files for the reflector and ambed makefiles. You should **not** modify these files by hand unless you really know exactly how they work. The rconfig will not start if it detects that an XLX or XRF server is already running. You can override this behavior in expert mode: `./rconfig expert`. If you do change the configuration after you have already compiled the code, it is safest if you clean the repo and then recompile.
 
 ### Compling and installing your system
 

rconfig

@@ -195,6 +195,11 @@ tcmodules_d='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
 g3support_d=false
 dbsupport_d=false
 
+# expert mode
+if [[ "$1" == ex* ]]; then
+	expertmode="expertMode"
+fi
+
 if [ -e reflector.cfg ]; then
 	source reflector.cfg
 else
@@ -202,18 +207,20 @@ else
 	sleep 1
 fi
 
-if [ -e $xlxserv ] || [ -e $xrfserv ]; then
+if [ ! -z ${expertmode+x} ]; then
-	echo -n "You cannot change the configuration right now beacuse there is an "
+	if [ -e $xlxserv ] || [ -e $xrfserv ]; then
-	if [ -e $xlxserv ]; then
+		echo -n "You cannot change the configuration right now beacuse there is an "
-		echo "XLX server running."
+		if [ -e $xlxserv ]; then
-	else
+			echo "XLX server running."
-		echo "XRF server running."
+		else
-	fi;
+			echo "XRF server running."
-	echo "===========${rcfg}============="
+		fi;
-	cat $rcfg
+		echo "===========${rcfg}============="
-	echo
+		cat $rcfg
-	echo "Please use radmin to uninstall the running server before attempting to modify the configuration."
+		echo
-	exit 1
+		echo "Please use radmin to uninstall the running server before attempting to modify the configuration."
+		exit 1
+	fi
 fi
 
 key='x'