Mailinglist Archive: opensuse (2831 mails)

[Carl Hartung <suselinux@xxxxxxxxxxxxx>]

On Monday 24 July 2006 09:34, stephan beal wrote:
> That problem was the reason i subscribed to this list ;).
>
> IIRC the lock file you need to remove is /var/run/zypp.pid.

Hi Stephan,

10.0 predates the new updater system delivered with 10.1, but you've got the 
right idea. :-)

Lucky,

First verify that you really have killed all yast processes... run 'top' in a 
shell (or in the alternate console.)

When you're certain there's nothing holding the rpm database open, look for an 
orphaned 'lock' file under /var/lib/rpm and delete it.

If the lock-up occurred with the last set released (I think) yesterday for 
10.0, there was one update for the kernel plus two or three more. Try running 
YOU and deselecting everything /but/ the kernel update, allow that update to 
be applied, reboot (necessary for kernel updates) and then run YOU again to 
apply the remaining patches.

In my experience, you need to apply kernel patches independently of any other 
patches, reboot and proceed with the rest to avoid problems like the one you 
experienced.

hth & regards,

Carl

-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx