Ctrl+C problems

Fixit7 · 03-15-2016, 07:11 PM

Quote:

Originally Posted by devnull10

ctrl+c works fine for me.

Does not work in Slacko 6.3

Ztcoracat · 03-15-2016, 08:46 PM

Run:

Code:

ps aux

That will give you the pid # and the description of the script or program running on the right.
Use the pid # with the kill cmd to stop it.

For example I'm running the gnome shell and the pid for it is:1024. If I wanted to kill it I'd run:

Code:

kill 1024

Wait until the script is done:-

Fixit7 · 03-15-2016, 09:03 PM

Looking for an automated way to kill it.

Ztcoracat · 03-15-2016, 09:20 PM

Quote:

Originally Posted by Fixit7

Looking for an automated way to kill it.

Most modern puppies include pprocess - it should be in the menu under "system" or "utility" or something, or you can start it from a terminal.
http://www.murga-linux.com/puppy/vie...882fe090c72533

Maybe give lxtask a try the Puppy pkg is on the page.

http://puppylinux.org/wikka/LxTask

The lxtask on this page is a bin file.
http://puppylinuxfaq.org/add-on-soft...nager-pet.html

rajahindustani · 03-18-2016, 12:19 AM

my ctrl c and ctrl z work properly...

Fixit7 · 03-18-2016, 07:43 AM

Ctrl C terminates a script if it is run from a console, but does not if started from a file manager.

Easiest way is killall [name of script]

rtmistler · 03-18-2016, 02:26 PM

Quote:

Originally Posted by chrism01

I'm trying not to just give you the answer, but

Code:

sleep 1 &
j=1


wait

1 of those lines needs changing, 2 need removing.
If you're sending the whole script into the background (as reqd) the you've got all the time in the world to figure out the correct kill cmd. Its an infinite loop (as reqd).
http://rute.2038bug.com/index.html.gz
http://tldp.org/LDP/Bash-Beginners-G...tml/index.html
http://www.tldp.org/LDP/abs/html/

Quote:

Originally Posted by chrism01

The clue is in the qn

You're just sending the sleep into the the background... Think about the requirement more closely.

@OP you need to pay attention to what chrism01 is telling you. They are correct, you have a "no wait" loop running a do-forever operation, basically, within your for 1-10 loop. I'm betting this makes CTRL-C hard, and I'm also wondering, sans personal experimentation whether or not you have a zillion (give or take) children being spawned with those background sleeps from within your do-forever loop. Why not look at the process list when you run it.

BW-userx · 03-19-2016, 07:45 AM

if you are going to be running it in the background off of the command line, which it looks like you already know how to do in post #5.

As you stated this, "My professor needs a demonstration from me and wants to see how i am killing the script. Ctrl^z and Ctrl^c are not working."

the word "demonstration" clearly indicates he just wants to see you preform the task. this is a no brainier if you stop and think about it enough

, and requires no coding whatsoever.

it is all command line driven using two terminals and knowing how to use the kill, pkill, or killall command.

All you're really missing is that part where you display "bang", within your code and you are done.

EXCEPT

the next posted question points out something very important too. It is termed overkill, and what are you waiting for seeings how you're already sleeping? Talk about overkill. Figure out that little riddle.

where only one letter in the alphabet is really needed, where then is a true statement needed? another riddle for you.

now go back up and read what @chrism01 had to say and think about it some more, until you get it, then hopefully you'll act on it properly. knowing what the term overkill means too would be important.

Then hopefully you'll get an A+ on this assignment.

(this post has been modified in accordance with some by-law that not even I am aware of)

cnamejj · 03-19-2016, 07:57 AM

This thread is ancient, revived by accident I suppose. Deleting my comments to avoid tricking others into continuing this.

chrism01 · 03-20-2016, 04:43 AM

Guys,

can I just point out that the qn & my prev responses are from 2010 ...

BW-userx · 03-20-2016, 12:56 PM

well if he has not figured it out by now then what is to be said of that?
or
I am really getting tired of people pulling old post and reviving them. I don't even get that board.

hydrurga · 03-20-2016, 01:02 PM

Quote:

Originally Posted by BW-userx

well if he has not figured it out by now then what is to be said of that?
or
I am really getting tired of people pulling old post and reviving them. I don't even get that board.

I've bookmarked this post of yours so that I can revive it in 2023.

Me too, but to be fair, I reckon a number of folk who've done that find the threads through Google etc. and don't notice the dates on the thread when they add a post to it.

BW-userx · 03-20-2016, 01:11 PM

@hydrurga

haha

chuckle chuckle

yeah that is the last thing I look for, when it was first posted. Too much is left to automation.

rtmistler · 03-20-2016, 06:21 PM

Quote:

Originally Posted by chrism01

Guys,

can I just point out that the qn & my prev responses are from 2010 ...

OK sorry, but ... well LQ does warn us about resurrecting very old threads. So whomever raised the thread up after many years, apparently ignored the warning which comes up before you post. The rest of us are guilty of not noticing that too, but we obviously do not receive warnings by the site once the thread was raised up.

LrodMC · 03-21-2016, 10:09 AM

In Ubuntu 14.04 LTS, you should be able to do CTRL + ALT + DEL, just like a windows. If you cannot do that, just search "System Monitor" in the start menu. Just look for the process "bash" in the system monitor window, and kill it using the "End process" button. If you can SEE the window and it is frozen, it is easier to go to terminal and type in the following command:

Code:

xkill

OR

Code:

sudo xkill

After entering any of the above commands, just simply click on the window you wish to kill.