[Rpm-maint] [rpm-software-management/rpm] RPM Query behavior via sudo vs user (Discussion #2322)

[Panu Matilainen]

The regular user doesn't have write-permissions on the shared database environment (those __db.* files), which is required to register even a read-lock in there. So when running as a regular user, rpm cheats by using a private environment, which amounts to no locking at all wrt a concurrent writer. As in, it's unreliable and broken but the alternative of not allowing any queries for regular user is not really an option either.

Note that this is specific to the deprecated Berkeley DB backend which has been entirely dropped upstream. The newer backends do not have such an issue.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2322#discussioncomment-4379806
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/2322/comments/4379806 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20221212/2c2c8ca2/attachment.html>