On 01/09/2020 21.33, J Leslie Turriff wrote:
On 2020-09-01 04:14:49 Carlos E. R. wrote:
On 01/09/2020 11.09, Freek de Kruijf wrote:
Op dinsdag 1 september 2020 10:57:32 CEST schreef Carlos E. R.:
On 01/09/2020 09.53, Freek de Kruijf wrote:
Op dinsdag 1 september 2020 02:40:06 CEST schreef Doug McGarrett:
Trying it with zypper in the console, it comes up with a conflict:
DESKTOP-4FH9U1P:/home/doug # zypper install artha System management is locked by the application with pid 30093 (/usr/bin/ruby.ruby2.7). Close this application before trying again.
You see the culprit is already given above, 30093.
So "kill -9 30093" will abort that process.
Don't.
Because this kills the tool without cleanup, and the flag file that signals the dattabase lock remains there, not deleted, and then we have a new problem to explain to Doug. :-/
I did do this often without ill effect. Maybe I just used "kill 30093" without the -9.
Yes, there is a difference :-) A polite signal should work, but I'm not fully sure.
I was under the impression that -9 is the default; but in any case, I've never had a problem with the lockfile from doing this.
No, the default is "TERM", ie, 15 (signal(7)). Using 9 is dangerous. The correct manner is first to exit the program if it responds, then a normal signal, and as a last resource, a 9. Yes, I had problems with the lock file, and seen other people having trouble with it asking here or elsewhere.
I did have fun discovering that 'sw-single' is the YaST "Software Management" tool. How these names are correlated is a mystery to me; especially, why single for a tool that works with multiple packages? :-)
Ancient history, I'd guess. :-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)