[Rpm-maint] [rpm-software-management/rpm] Don't modify interupts if db is read only (#251)

Jeff Johnson notifications at github.com
Fri Jul 14 13:25:48 UTC 2017

@mischroe: DB_PRIVATE has its own associated durability/signal problems, including that ^C is masked while installing, and with the transaction lock being for exclusive writers, not readers.

Truly ^C handling needs to be solved intelligently, not with convoluted contortions to BDB configuration. Been there, done that, hacks to BDB configuration and verification ever worked well enough. Adding ~10-15 checks on signal receipt and calling rpmdbClose exits within seconds.

The entire issue is that rpmdbClose needs to be called before exit, particularly with ^C.

And most of the complaints about "corruption" (for the entirely different case of "kill -9") disappear if 10 lines of code are added to automate DB_RUNRECOVERY.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20170714/1a15b15d/attachment.html>

More information about the Rpm-maint mailing list