Re: How to forcibly abort a command in a terminal window?
On Mon, 5 Sep 2016 09:06:27 -0500
Richard Owlett <rowlett@cloud85.net> wrote:
>On 9/5/2016 8:35 AM, Jonathan Dowland wrote:
>> On Mon, Sep 05, 2016 at 08:13:03AM -0500, Richard Owlett wrote:
>>> Thank you.
>>> Sometimes harware reset is the only thing.
>>> The cp command was crudded up by human error ;/
>>
>> Your ^C would eventually be honoured by cp. The result will be an incomplete
>> copy, but the filesystem should be in a consistent state. Performing a hardware
>> reset could result in filesystem corruption (which a journalled filesystem
>> would correct: but not something like FAT32 as commonly used on USB sticks).
>>
>
><GRIN> promptness of abort was higher priority than file system
>integretity.
>I date from 8085 being a new device ;/
>
>
I open a second terminal, then use ps -A to find the command. I can
kill it with "sudo kill ????" which kills the job number. It is not
always instant, but faster than ctrl-c for some things, including rsync
and cp .
--
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM. [http://keepingdreams.com]
Reply to: