20 Mar
2006
20 Mar
'06
21:17
On Mon, 20 Mar 2006, Juan Erbes wrote:
3:tpctl-kmp-default ########################################### [100%] warning: waiting to reestablish exclusive database lock
I think ZMD should wait a bit longer to give the pre-/post-inst scripts to do their duty first.
When I use smart to upgrade the system, I got the same errors when the zmd daemon are active ( "warning: waiting to reestablish exclusive database lock" and the excesive memory usage, about 1,3 GB of virtual memory). When I kill the zmd daemon, smart works fine.
That's a known feature / bug ;)
You will continue to support smart?
Of course. Regards Christoph