Feature #3580
ensure that rate_ctr_init() is called from main application
Start date:
09/20/2018
Due date:
% Done:
100%
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
History
#1 Updated by neels about 2 years ago
- Related to Bug #3579: osmo_bsc_main.c apparently fails to call rate_ctr_init() added
#2 Updated by laforge over 1 year ago
- Assignee set to laforge
- % Done changed from 0 to 90
#3 Updated by laforge over 1 year ago
- Related to Feature #3987: introduce libosmocore_init() to replace individual initialization calls added
#4 Updated by laforge over 1 year ago
- Status changed from New to In Progress
#5 Updated by laforge over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
patch merged
