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/OpenBSC@lists.osmocom.org/.
Alexander Chemeris alexander.chemeris at gmail.comOn Jun 2, 2015 9:26 AM, "Holger Freyther" <holger at freyther.de> wrote: > > > > On 30 May 2015, at 21:43, Alexander Chemeris < alexander.chemeris at gmail.com> wrote: > > > > Otherwise you have to restart BTS or at least break the RSL connection > > to apply the change. > > Yes we certainly should apply modifications at runtime but probably not by adding > auto-update to each command. When I change LAC/CI/ms_max_power I don’t want > to update the SI three times. > > We really need to have a “commit”/“apply” kind of command that applies OML and > RSL modifications. I agree that transactional functionality would be nice and I had been thinking about this. But it's a big change which should be well planned and requires considerable effort to go through all commands and split configuration from application. One issue is that we'll need to create "shadow" registers for the non applied settings. E.g. in case of power control, the setting was actually applied at the BSC part of the control (it was using the setting variable directly), but was not propagated to the BTS party, which was really confusing from a user perspective. In short - I agree that such feature would be nice, but I don't think this is a showstopper for this patch, because it just makes things more consistent. Btw, control interface also applies the change immediately. Having vty and control to diverge is quite confusing. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20150615/98ac7891/attachment.htm>