Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
06-15-2006, 04:57 PM
|
#1
|
|
Member
Registered: Feb 2005
Location: Kuala Lumpur, Malaysia
Distribution: Fedora Core 5
Posts: 121
Rep:
|
How to know which process can be stop
I want to stop a process from running but I dont know which process is suitable to be killed cause I'm afraid that if I stop the wrong process, it might make the system unstable. Any suggestion on stopping a process? Is it wise to stop a process from the /usr or /sbin directory which is runned by root?
|
|
|
|
06-15-2006, 05:42 PM
|
#2
|
|
LQ Newbie
Registered: May 2006
Location: Sydney, Australia
Distribution: Red Hat 7.3
Posts: 27
Rep:
|
If you know the name of the process, eg sendmail, just type ps -aux | sendmail, and that will list all processes with sendmail in the name, along with their PIDs (process id's).
then just kill the process by number. ie if it's pid 567, just kill 567 will do it.
if you want to get a list of al the processes runing, and then sit down and pore over it, type 'ps -aux > processes.txt
That will send a detailed list of all the processes to the file processes.txt
then you can print it, and try to work out what each is/does.
if you see a process called xyz, look for a man page for that program . 'man xyz' will do that. That will get you info on most of the stuff that's running, and you can decide which ones you need/don't.
Anything you want to stop from loading at bootup, remove the S* file from /etc/rc.d.rc3.d (to see the names of the files kicked off at startup, type 'ls -l /etc/rc.d/rc3.d/S*' ie list all the files, that start with S, in that directory.
Or if you are running X, use the services program to select which ones you want/don't want.
Does this help?
Griffo
|
|
|
|
06-15-2006, 07:04 PM
|
#3
|
|
LQ Veteran
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,797
|
If you don't know WHICH process you want to stop, then how do you know that you want to stop something?? What problem are you trying to solve......
if you do "ps" you will see all the processes. (see man ps) If you don't know what something is, then you can bet that killing it might not be good. On the other hand, you probably won't do irreversible damage by experimenting (After backing up all your data, of course...  )
|
|
|
|
06-15-2006, 11:40 PM
|
#4
|
|
Member
Registered: Aug 2001
Location: ChristChurch New Zealand
Distribution: Ubuntu
Posts: 223
Rep:
|
How about this for a notion.....
If you are a Good Guy, you are not running as super user (root), right!?
Thus you can kill all and every process in sight.
And the system will keep running.
Since the kernel won't allow you to kill any process that is not your user process.
Your window manager may die, your editor may get killed, the panel may vanish but who cares, the system keeps chugging along.
Logout and login again and all is fine.
Useful commands relating to processes....
ps auxw | less
List all processes
pstree -pal
List process tree structure.
top
See which process is hogging
killall -9 firefox-bin
Tries to kill all firefox instances.
su
/etc/init.d/httpd restart
exit
Kills and restarts the web server.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:42 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|