A way to ensure rpm database robustness?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

 

I have a simple question and sorry if it was asked before and I just didn’t find it in archives.  

Suppose we run rpm operation (installation, update or anything) on an embedded device and power suddenly goes off. This can happen if user removes the battery for example.

In such cases, rpm database can get corrupted since the operation was stopped in the middle. Rpm database can be rebuild after, but this is quite annoying to do. Is there any ways to ensure that database stays sane even in such cases? Of course some wrapper can be used for rpm to do the checks, backup database and etc., but does rpm itself have anything for it?

 

Best Regards,
Elena.

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux