Osmocom Mobile Switching Centre
Go to file
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
debian debian: Fix dependencies 2015-01-21 13:24:38 +01:00
hlrsync hlrsync: Sync SMS from the web db to the hlr. 2009-08-14 21:33:34 +02:00
linux-kernel new kernel patch for multiple virtual interfaces 2009-08-10 23:36:53 +02:00
openbsc osmux: Initialize the socket only once 2015-01-21 16:56:53 +01:00
wireshark Fix bogus message labelling in wireshark OML dissector 2011-09-19 09:19:09 +02:00
README first commit 2011-02-05 20:26:25 +01:00

README