RE: Operating systems Wars!
March 12, 2017 at 5:48 pm
(This post was last modified: March 12, 2017 at 5:57 pm by pocaracas.)
(March 12, 2017 at 5:27 pm)Mathilda Wrote: Why oh why does it take so long to kill an application in Windows? You have to wait for ages, and then go through loads of confirmations, as if you had accidentally told selected an application in the task manager and asked to kill it. And then,Windows stars searching for a solution to the problem. Has it ever, in the history of Windows ever found a solution? I was once curious about it and let it continue searching for a solution while I went and made some tea. As expected, no solution found.
In Linux, type 'top' (equivalent to task manager)
Look at the process id
Type the letter K
Type the process id
Hit enter
Process dies. Quickly.
top?
pfft... how inefficient?
> ps xua|grep [program name]
> kill -9 [pid]
Btw, look into a cool top-enhanced called htop.
(March 12, 2017 at 6:02 am)pocaracas Wrote:(March 12, 2017 at 4:38 am)Cthulhu Dreaming Wrote: Try MobaXterm. The free version is pretty limited in the number of profiles it will save but if you're willing to use a Unix-like shell, it has an internal terminal session which blows away Putty.
I use it at work to access dozens of systems via ssh, stop/scp, tunneling, xterm, etc etc etc.
Oh...it has an X server built in...
I used XMing for that... Before my recent bout with Asus warranty where, to replace a faulty screen, they decided to turn my hard drive into a OOBE (Out Of Box Experience...aka all programs and files gone and back to an all new Windows).
I'm so going to try that moba. Thanks for the tip!
My raspbian doesn't like the X-server on this thing...
Oh well.... at least it does the tunnel I want automatically at startup...
