On 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