summaryrefslogtreecommitdiffstats
path: root/include/osmocom/vty
Commit message (Collapse)AuthorAgeFilesLines
* select: use namespace prefix osmo_fd* and osmo_select*Pablo Neira Ayuso2011-05-071-1/+1
| | | | | | | | | Summary of changes: s/struct bsc_fd/struct osmo_fd/g s/bsc_register_fd/osmo_fd_register/g s/bsc_unregister_fd/osmo_fd_unregister/g s/bsc_select_main/osmo_select_main/g
* vty: move vty_out_rate_ctr_group prototype to osmocom/vty/misc.hPablo Neira Ayuso2011-03-282-1/+11
| | | | Before this patch, it was in osmocom/core/rate_ctr.h
* include: reorganize headers file to include/osmocom/[gsm|core]Pablo Neira Ayuso2011-03-231-2/+2
| | | | | | | | | | | | This patch moves all GSM-specific definitions to include/osmocom/gsm. Moreover, the headers in include/osmocore/ have been moved to include/osmocom/core. This has been proposed by Harald Welte and Sylvain Munaunt. Tested with `make distcheck'. Signed-off-by: Pablo Neira Ayuso <pablo@gnumonks.org>
* vty: integration with logging frameworkPablo Neira Ayuso2011-03-191-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The logging categories are registered by the applications, like osmo-nitb, during startup. Thus, the VTY have to provide the logging commands according to the logging categories that the application has registered. Before this patch, the VTY contained the logging categories hardcoded. Thus, any change in the logging categories by the application would not be shown by the VTY. So far, this was not a problem because all applications used the same logging categories. However, according to what Harald told me, this may be a problem in the future. This patch resolve the lack of integration between the logging framework and the VTY by generating the VTY logging commands from the logging categories registered. Since this patch changes one function of the libosmocore API, it follows another patch for the openbsc application to get in sync with the new function layout. I have reworked and renamed the functions: * log_vty_category_string() * log_vty_level_string() to provide the new ones that generate the exact output that VTY requires. This patch does not release the memory allocated by talloc_zero_size() to store the VTY strings for the commands and the description. I found no exit function that can clean up resources that were allocated.
* LOGGING: remove duplicated code between vty-logging and cfg-loggingHarald Welte2011-02-181-0/+2
|
* LOGGING: configure logging from the vtyHarald Welte2011-02-181-0/+1
| | | | | We can now configure logging to (multiple) files, stderr and syslog from the vty command line in a persistent way (config file)
* vty: Add functions to access index and nodeHolger Hans Peter Freyther2010-09-141-0/+2
| | | | | | It is easier to call these two functions from bindings than wrapping the vty structure and figuring out the alignment of the enum on all different ABIs.
* vty: Make the talloc ctx extern void* to avoid duplicate symbolsHolger Hans Peter Freyther2010-08-311-1/+1
|
* vty: Add a new callback to let code decide if it is a config node or notHolger Hans Peter Freyther2010-08-261-0/+1
|
* vty: Forward delcare the logging command.Holger Hans Peter Freyther2010-08-041-0/+2
|
* vty: Mark app info strings as const char*.Holger Hans Peter Freyther2010-06-081-3/+3
|
* [VTY] Remove all application specific VTY node definitions from enumHarald Welte2010-05-311-41/+2
|
* [VTY] Introduce "struct vty_app_info" for vty_init() functionHarald Welte2010-05-252-6/+10
|
* make sure we actually install the vty headersHarald Welte2010-05-251-2/+4
|
* Create libosmovty as library from OpenBSC VTY functionsHarald Welte2010-05-257-0/+758