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.deOn Tue, Sep 29, 2015 at 03:25:15PM +0200, Holger Freyther wrote: > > Am not clear yet how an error in a protocol callback should propagate to > > the main loop and barf there. Certainly something grave should happen. > > “log an error” means LOGP(BLA, LOGL_ERROR, “Something bad happened %d\n”, rc); yes yes, instead I meant: when a fatal error happens in a callback, how do I make the main loop exit. Specifically, if SGSN registration failed, then do (from the cb), in order of effort: LOGP and... - ignore otherwise, SGSN services may not work. - exit(-ENOTREGISTERED). - set a flag to break main loop. - set a timer at program start, and if we're not registered after a while, exit. - ... Is there a typical way for the osmo universe? ~Neels -------------- 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/20150930/653a1df3/attachment.bin>