On Fri, May 21, 2010 at 11:20:02PM -0400, Jeff Johnson wrote:
> > Right. So it sounds like
> > 1) __db* files can't be turned off since for most users they are useful (not
> > for us though).
> I'm not sure how you arrive at this conclusion. Dataabses (with concurrent access) locks,
> the locks are in __db* files, and only userst need locks?!?
No, I mean other rpm users.
We don't have users or concurent rpm use.
> But there are many alternatives, including just disabling all locks.
> > 2) I could hack rpm to find all the exit paths or wrap it and auto delete
> > the db files on exit
> Its easier than that. There is code that removed __db* files at end-of
> execution. It very much was not the right thing to do, but Have fun!
> > 3) if I have an rpmdb synced over a machine that has non matching __db*
> > files, nothing really bad will happen, but rpm may act weird and it's
> > just better not to get in that situation, potentially via #2 or other
> > means.
> Why sync files that aren't useful in the first place?
That's the point, we don't sync __db* files but some local debugging run
on a machine might create them and then they would be a mismatch with an
rpmdb rsync on top.
Deleting them in this case is the best way to make sure we don't have a
Thanks for your help,
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
Received on Sat May 22 06:16:34 2010