NITB: high cpu usage and "crossed" messages when SMS table grows

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/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Wed Mar 15 13:22:23 UTC 2017


On Tue, Mar 14, 2017 at 02:37:00PM +0100, Keith wrote:
> We should probably fix this up and create some internal purging of sent SMS?

> > Sending SMS to the wrong recipient though is probably worth fixing. That
> > should really not happen.
> No, it makes people rather irate. :-(

The social dimension of it is potentially quite destructive :P
"Wait what!? *Who* is *Mandy*!?!?"

Plus the IMSI == Inf thing.

I fully agree and would love to jump in and help out, but unfortunately I can't
divert my attention from the current commitment, at least not now...
Switching to an external SMSC is probably also going to take Inf ms.

~N

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170315/260b5242/attachment.bin>


More information about the OpenBSC mailing list