On Sat, Jun 29, 2013 at 10:34:25AM +0200, Harald Welte wrote:
Good Evening,
Ah, ok. I was (erroneously) assuming that the PCU
would simply exit at
the time the connection to osmo-bts drops. This way, it re-spawns and
re-initializes nicely when the BTS is sending the next
PCU_IF_MSG_INFO_IND. However, I may be writing too much Erlang code in
recent days, hence my 'let it exit and re-spawn' attitude ;)
ironically Harald and me were bitten by incomplete bssgp reset after
the exit/restart of a bts/network. sysmocom would prefer if the PCU
would fail/exit instead of an almost working reset. Currently a shell
script and in the future systemd will relaunch the osmo-pcu process.
I can prepare a patch that adds this behavior as VTY option unless
everyone agrees that the process should exit.
cheers
holger
--
- Holger Freyther <hfreyther(a)sysmocom.de>
http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Schivelbeiner Str. 5
* 10439 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte