-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Howarth wrote: > My comment is: it won't work because yum creates a lock file > specifically to prevent this from happening. > > Paul. > Not actually true. If you are running the secondary copies of yum as a non-privileged user, then this works - for some values of 'works' ;-) What I have observed is that during updates to the repository data, non-privileged searches fail, either because of inconsistent metadata or with some ugly python backtraces indicating problems accessing the db. Once the root-owned yum finishes modifying the cache files, searches work for non-privileged users as expected. I don't know if doing this is a good idea, or even expected behaviour - ymmv :-) Cheers, Bryn. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDO+h46YSQoMYUY94RApO5AKCXHVt7yVwa7NnFfUFC0xWQmwt/IQCfbPXw Ixzpr1j465uN97YFjPh4wAE= =3X6J -----END PGP SIGNATURE-----
