[Rpm-maint] [PATCH] Add API to completely disable librpm's use of Unix signal handlers

Florian Festi ffesti at redhat.com
Tue Feb 17 12:07:38 UTC 2015

Sorry, for the last response. DevConf takes its toll...

On 01/23/2015 04:07 AM, Colin Walters wrote:
> Numerous consumers of librpm use it in a pattern where they're
> constructing fresh chroots.  For example, rpm-ostree operates this
> way, and is used to provide atomic upgrades in concert with rpm.
> If the process dies due to SIGINT or another signal, the root can
> simply be discarded.
> Currently today, rpm-ostree undoes the signal handlers after loading
> librpm so that Control-C does what I want, but there's still a race
> condition where the interrupt can be lost.
> Add an API so callers can disable the behavior.

Is there any chance someone would want to switch them back on? My gut
feeling tells me this should rather be rpmsqSetInterruptSafety(int on);



Red Hat GmbH, http://www.de.redhat.com/ Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Charles Peters

More information about the Rpm-maint mailing list