@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:
https://github.com/rpm-software-management/rpm/pull/251#issuecomment-315358868
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to