libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	include: reorganize headers file to include/osmocom/[gsm\|core]	Pablo Neira Ayuso	2011-03-23	1	-154/+0
\| \| \| \| \| \| \| \| \| \| \| \|	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 framework	Pablo Neira Ayuso	2011-03-19	1	-3/+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: configure logging from the vty	Harald Welte	2011-02-18	1	-0/+13
\| \| \| \| \|	We can now configure logging to (multiple) files, stderr and syslog from the vty command line in a persistent way (config file)
*	LOGGING: Add syslog log target	Harald Welte	2011-02-17	1	-0/+2
\|
*	LOGGING: Pass the log level down to the log target output function	Harald Welte	2011-02-17	1	-1/+2
\| \| \| \|	This will be required for mapping osmocore log levels to syslog priorities.
*	misc: Move the static_assert from logging to the utils	Holger Hans Peter Freyther	2011-01-16	1	-1/+0
\| \| \| \| \| \|	This is just an ordinary macro, no specific reason to have it in logging.h. This was compile tested with code from our osmo family.
*	logging: add missing include file changes for last commit (logfile)	Harald Welte	2010-08-25	1	-0/+5
\|
*	logging: rename tgt_stdout to tgt_file	Harald Welte	2010-08-25	1	-1/+1
\|
*	move hexdump() from logging.c to utils.c	Harald Welte	2010-07-30	1	-1/+0
\|
*	logging: add log_vty_{level,category}_string()	Harald Welte	2010-05-11	1	-0/+4
\|
*	logging: introuduce log_level_str() to obtain the name of a log level	Harald Welte	2010-05-11	1	-0/+1
\|
*	rename 'debug' interface to 'logging' interface	Harald Welte	2010-03-26	1	-0/+130
	It's not really about debugging, but about generic logging...