This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".
The branch, master has been updated
via ab2454e776f1a4bc4977ef48ec2844600f85176b (commit)
via 9f64c54040857079fa5ca35bf522d3befe7ac362 (commit)
from 4d87e22980edb5a0ec170801980f76c837183b32 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=ab2454e776f1a4bc4977ef48ec2844600f85176b
commit ab2454e776f1a4bc4977ef48ec2844600f85176b
Author: Harald Welte <laforge at gnumonks.org>
Date: Thu Jul 20 01:19:18 2017 +0200
bsc_vty: Don't allow timers of zero (0)
It typically doesn't make sense to configure any of the GSM RR timer
to 0 (Seconds). In fact, accidentially configuring any of the timers
to zero might have severe side effects, such as "stuck channels"
described in https://osmocom.org/issues/2380
Change-Id: I517828f2f0c80ec01cb63648db2626f17a67fe57
http://cgit.osmocom.org/openbsc/commit/?id=9f64c54040857079fa5ca35bf522d3befe7ac362
commit 9f64c54040857079fa5ca35bf522d3befe7ac362
Author: Harald Welte <laforge at gnumonks.org>
Date: Thu Jul 20 01:47:39 2017 +0200
GSM timers: User reasonable defaults; don't save if equal default
A number of the GSM timers (including T3109) had no reasonable
default values if not specified in the VTY / config file. Together
with unconditional writing to the config file, this created
config files with a persistent setting for important timers as '0'.
To make things worse, many of our example cofig files suffered from the
same problem.
Let's avoid this from happening by
* having reasonable defaults if nothing specified in the config file
* conditionally savingg timers only if they differ from default
* reject any timer values that state zero during start-up (see previous
commit)
Change-Id: Iaac0bfca423852b61d8b9eb1438157ef00d0d8c8
Closes: OS#2380
-----------------------------------------------------------------------
Summary of changes:
openbsc/doc/examples/osmo-bsc/osmo-bsc.cfg | 12 --------
.../osmo-nitb/bs11/openbsc-1bts-2trx-hopping.cfg | 11 --------
.../examples/osmo-nitb/bs11/openbsc-1bts-2trx.cfg | 2 --
.../examples/osmo-nitb/bs11/openbsc-2bts-2trx.cfg | 2 --
openbsc/doc/examples/osmo-nitb/bs11/openbsc.cfg | 2 --
.../osmo-nitb/nanobts/openbsc-multitrx.cfg | 11 --------
openbsc/doc/examples/osmo-nitb/nanobts/openbsc.cfg | 11 --------
.../osmo-nitb/nokia/openbsc_nokia_3trx.cfg | 2 --
openbsc/doc/examples/osmo-nitb/rbs2308/openbsc.cfg | 12 --------
.../doc/examples/osmo-nitb/sysmobts/openbsc.cfg | 11 --------
openbsc/include/openbsc/gsm_data.h | 12 ++++++--
openbsc/src/libbsc/bsc_vty.c | 33 +++++++++++++---------
openbsc/src/libbsc/net_init.c | 9 +++++-
13 files changed, 37 insertions(+), 93 deletions(-)
hooks/post-receive
--
Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)