Hi,รง
I don't know how, but the chair-keyboard interface got two yast sessions
running, both trying an online update, and both failing complaining
there was another program using the database.
So far, "normal".
The problem was trying to kill them both. One of them had to be forced
kill, and revived: but with no display window in kde. I could see in top
a "y2base" that I had to kill, but when I tried top complained there was
no such pid; true enough, the pid had changed. Then I noticed that on
almost each top refresh (2") the PID changed. Finally, via "ps afx" I
discovered it's parent, yastonlinesomething, and killed that.
Yast is running now alright.
So... couldn't yast-online figure another yast-online was already
running before starting, and exit with an informative message box? Now
it discovers the problems when it fails to grab the rpm database, it seems.
--
Cheers,
Carlos E. R.
(from RC1)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
