First, to find out the PID, do:
ps -ef | grep YOUR_PROGRAM_NAME
Usually, but not always, (man ps will tell you), the second column has the
PID.
Then you can:
kill -TERM <PID>
That should do it, if not:
kill -9 <PID>
Roger
says...
You can find all the processes "owned" by a specific user by using the "-Quote:> Ok maybe this is not the right group to ask, but i have this problem, i have
> a Unix account, and the other day i was experimenting with nohup, i made a
> program to test it, and now i cannot stop it, any ideas?
Once you use this command to find your own processes you can kill it by
using the kill command as follows :
kill -9 process_id
The "-9" causes a signal to be sent to the process that can't be caught
or ignored, therefor the process should die.
--
---------
Barry Kimelman
Winnipeg, Manitoba, Canada
hence should only be used as a last resort.Quote:>Once you use this command to find your own processes you can kill it by
>using the kill command as follows :
> kill -9 process_id
>The "-9" causes a signal to be sent to the process that can't be caught
>or ignored, therefor the process should die.
--
bringing you boring signatures for 17 years
I wish to use nohup to generate a numerical database. So nohup is the
choice. Like this:
nohup myprogram > nohup.out 2>&1 &
When I logout and login again to check, myprogram is not running
there.
Any one had similiar experience? It seems that nohup is not working as
intended.
Jinsong Zhao
2. Which video card better supported in Linux?
6. Mwave card
8. DSO question
10. NOHUP Question
12. nohup question