ensure that rate_ctr_init() is called from main application
just now I noticed that osmo-bsc fails to initialize the rate_ctrs properly.
It would be good to have some internal mechanism that ensures this never forgotten.
For example, in rate_ctr_group_alloc() or osmo_stats_vty_add_cmds(), we could check an internal flag and assert if false?
#2 Updated by laforge about 2 months ago
- Assignee set to laforge
- % Done changed from 0 to 90