Ticket #17 (assigned enhancement)

Opened 3 years ago

Last modified 2 years ago

RPMTRANS_FLAG_NOSIGNALS

Reported by: romanov Assigned to: pmatilai (accepted)
Priority: minor Milestone: rpm-4.10.0
Component: rpm Version: RPM Development
Keywords: Cc:

Description

Currently (as far as I can see) librpm processes SIGINT-like signals itself (e.g. function rpmdbCheckSignals calls exit(EXIT_FAILURE)). It turns out that an librpm using application cannot react on signals somehow differently. Is it possible to include the capability of custom termination signals handling in the next version of RPM? It could be seen this way for an application:

rpmtsSetFlags(ts, RPMTRANS_FLAG_NOSIGNALS);

Change History

12/16/08 14:31:09 changed by romanov

  • summary changed from RPMTRANS_FLAG_NOTERM to RPMTRANS_FLAG_NOSIGNALS.

12/18/08 07:39:46 changed by pmatilai

  • status changed from new to assigned.

No disagreement there, librpm should have means for API users to provide their own handlers for termination conditions, unconditionally calling exit() / _exit() from a library is just nasty.

This has been on my mental todo-list for some time, but better to have it tracked here.

10/06/10 06:25:34 changed by pmatilai

  • milestone changed from rpm-4.8.0 to rpm-4.10.0.