https://bugzilla.novell.com/show_bug.cgi?id=464680
User lslezak@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464680#c7
Ladislav Slezak changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #7 from Ladislav Slezak 2009-03-02 06:46:42 MST ---
The log contains these messages from the failed SM start:
2009-02-27 19:59:28 <5> linux-dqhf(6873) [zypp] Exception.cc(log):133 Close
this application before trying again.
2009-02-27 19:59:28 <5> linux-dqhf(6873) [zypp] Exception.cc(log):133
PkgFunctions.cc(zypp_ptr):103 RETHROW: ZYppFactory.cc(getZYpp):366: System
management is locked by the application with pid 2863 (/usr/lib/YaS
T2/bin/y2base).
2009-02-27 19:59:28 <5> linux-dqhf(6873) [zypp] Exception.cc(log):133 Close
this application before trying again.
2009-02-27 19:59:28 <3> linux-dqhf(6873) [Pkg] PkgFunctions.cc(Connect):165
Error in Connect: FactoryException: System management is locked by the
application with pid 2863 (/usr/lib/YaST2/bin/y2base).
Close this application before trying again.
Process 2863 is still running and prints messages
2009-02-27 20:02:21 <1> linux-dqhf(2863) [satsolver] PoolImpl.cc(logSat):81
installing old packages
2009-02-27 20:02:21 <1> linux-dqhf(2863) [satsolver] PoolImpl.cc(logSat):81
resolving job rules
to the log.
So there is no "dangling" lock, there is another Yast instance running and Yast
behaves correctly regarding to the locks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.