I have seen the UsrGetConfigIos() function to
occasionally return a "can't read Config: no such
variable" error message. (Unfortunately I don't
remember the exact circumstances. Conceivably the
reply from the router may have timed out so there was
no "end" line at the end.)
As the $Config variable gets declared only inside an if
block but its value may be read subsequently no matter
whether or not we have been inside that if block in the
first place, it would seem to be a good idea to either
initialize the Config variable even if we don't get inside
that if block, or else to produce a more helpful error
message telling the user what was wrong with the
router's reply (rather than with the syntax of the TCL
script).
The simplest workaround (always initialize the Config
variable by setting it to an empty string) is implemented
in the version of the script uploaded as part of this bug
report.
libusrget.tcl