Holger Hans Peter Freyther 9d1a17e15f osmux: Initialize the socket only once ... The per BSC code didn't guard against the init already having been executed. This lead to: Adding a osmo_fd that is already in the list. <000b> bsc_nat_vty.c:1200 Setting up OSMUX socket So a new socket got created and the old one leaked. Luckily Linux appears to allow to bind multiple times so we were able to just read from the new one. Use the same guard that is used on the MGCP MGW. Re-order the log message to say "Setting up" before we actually do that. I manually verified that osmux_init is called at most once. The log message was spotted by Roch		2015-01-21 16:56:53 +01:00
..
Makefile.am	bsc: Move gsm_subscriber_base.c to libcommon	2014-11-11 22:52:21 +01:00
bsc_filter.c	nat: Remember the original dest local reference in the parsed struct	2013-09-03 15:04:43 +02:00
bsc_mgcp_utils.c	mgcp: Move the "codec" params to a struct	2014-09-02 08:25:49 +02:00
bsc_nat.c	Use port number #defines for VTY and CTRL ports	2014-08-24 17:54:49 +02:00
bsc_nat_ctrl.c	nat: Fix compiler warning about unknown prototype	2014-08-29 11:42:26 +02:00
bsc_nat_filter.c	nat: Introduce reject cause to bsc_nat_acc_lst_entry	2014-01-20 10:13:36 +01:00
bsc_nat_rewrite.c	adopt recent IPA related symbol rename	2014-08-20 23:47:56 +02:00
bsc_nat_rewrite_trie.c	nat: Allow to use the prefix lookup to rewrite numbers	2013-07-31 16:36:40 +02:00
bsc_nat_utils.c	nat: Introduce a config free for the test and fix valgrind issues	2014-08-29 11:42:34 +02:00
bsc_nat_vty.c	osmux: Initialize the socket only once	2015-01-21 16:56:53 +01:00
bsc_sccp.c	nat: Rename "struct sccp_connections" to "struct nat_sccp_connection"	2013-04-16 09:53:13 +02:00
bsc_ussd.c	adopt recent IPA related symbol rename	2014-08-20 23:47:56 +02:00