On Wed, 2003-04-30 at 11:40, Warren Togami wrote:
> When rpm appeared to hang, did you check the running processes to be
> 100% sure that rpm was not running anymore before erasing the locks?
Well "check" wouldn't be exactly the right word for it, but I did leave
it for quite a while to see if it did anything. What would be the best
way to check - just look in System Monitor and see if the CPU > 0% for
rpm?
> Note that --rebuilddb should almost never be needed. I myself have
> never needed it during rpm-4.2 through the Phoebe betas and Shrike.
> Erasing the locks has been sufficient for fixing RPM problems for me.
Good to know. Thanks.
Best, Darren
--
=====================================================================
D. D. Brierton darren@xxxxxxxxxxx www.dzr-web.com
Trying is the first step towards failure (Homer Simpson)
=====================================================================
