Feature #3580
ensure that rate_ctr_init() is called from main application
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/20/2018
Due date:
% Done:
0%
Spec Reference:
Description
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?
Related issues
