vty: writing the configurations results in an invalid configuration
Use default configuration, after the PCU is started and conncted to the BTS,
call `write` via vty.
vty: Optionally Set/replace cfg file during cmd 'write file'
This way if the process is started with no file associated (eg. no -c
param and default cfg path doesn't exist), config can be later saved
into a file by passing the parameter. Otherwise, until now this message
Can't save to configuration file, using vtysh.
#1 Updated by pespin over 1 year ago
I could not see any issues regarding this ticket.
I tried with my usual config as well as with the example config from osmo-pcu/doc/examples/osmo-pcu.cfg, then connect it to the BTS, then on the VTY I do "write" and restart osmo-pcu -> it starts correctly.
I then tried running without any config file as parameter (and no osmo-pcu.cfg present in $PWD). But then if I call "write" in VTY, I get:
# write Can't save to configuration file, using vtysh.
#2 Updated by pespin over 1 year ago
- Status changed from New to Feedback
With this patch, I was able to start osmo-pcu with no cfg file and then save it into a file. I can also start osmo-pcu with that generated cfg file with no problem, so I think the issue is not longer present and can be closed. Leaving as feedback assigned to @lynxis.
https://gerrit.osmocom.org/c/libosmocore/+/15609 vty: Optionally Set/replace cfg file during cmd 'write file'