fixeria has uploaded this change for review.

View Change

VTY: fix ambiguity in BTS specific command definitions

Most of the BTS specific VTY commands restrict BTS number to '<0-0>',
while bts_c0_power_red_cmd has '<0-255>'.  This confuses libosmovty:

  OsmoBTS# bts ?
    <0-0>    BTS number
    <0-255>  BTS Number

  OsmoBTS# bts 0 ?
  % Ambiguous command.

  OsmoBTS# bts 0 c0-power-red 0
  % Ambiguous command.

Let's stick to '<0-0>', we don't support multiple BTS anyway.

Change-Id: I937ac421143678b97627c1bc4fe573831ce097f6
---
M src/common/vty.c
1 file changed, 1 insertion(+), 1 deletion(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-bts refs/changes/12/27412/1

diff --git a/src/common/vty.c b/src/common/vty.c
index 97bd658..8925999 100644
--- a/src/common/vty.c
+++ b/src/common/vty.c
@@ -1329,7 +1329,7 @@
 
 DEFUN(bts_c0_power_red,
       bts_c0_power_red_cmd,
-      "bts <0-255> c0-power-red <0-6>",
+      "bts <0-0> c0-power-red <0-6>",
       "BTS Specific Commands\n" BTS_NR_STR
       "BCCH carrier power reduction operation\n"
       "Power reduction value (in dB, even numbers only)\n")

To view, visit change 27412. To unsubscribe, or for help writing mail filters, visit settings.