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 Wed, Mar 20, 2019 at 06:12:30PM +0100, Pau Espin Pedrol wrote: > > Another topic that I forgot to list is signal handling. I would think it makes > > sense to move the SIGUSR1/SIGUSR2 handling into libosmocore now, particularly > > as we have the root talloc context[s] in libosmocore with my related patches. > > It just sucks to have to have a SIGUSR1->talloc_dump code snippet in each and > > every of our programs. > > Please don't. Let's allow apps decide how they handle user-defined signals > and not try doing everything in a generic library. I think it's better to avoid the code dup in each application, have well-defined standard handlers once. Thinking in terms of one global libosmocore subsystem config struct, this could be switch-off-able. If it were implicit any application can easily put other signal handlers in place after the fact. ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20190321/fbd02f92/attachment.bin>