Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I got an obnoxious apache webserver that I am trying to reinstall. And after uninstalling it fully (on a Debian 6.0 system), the darn thing is still running.
Kill off the process, it gets restarted.
Ok, lets get the big guns: I go ahead and erase all executables and directories belonging to apache... and...
scary scary, the DARN THING STILL RESTARTS...
HOW?????
In my book that is quite impossible. Where is it restarting from??
I suspect that the new automatic restart daemon is responsible for this. Is there any documentation on how that works?
How can apachectl still be installed if I removed all the executables??
What does actually restart the apache server (or any daemon) automatically when it crashes (or gets killed by signal)?
I know that many people must be having this problem with obnoxious daemons that just won't stay dead after you shoot them in the head ;-)
It is good to finally have auto restart, but this is the dark side of it.
Does Linux cache executables in memory, even after the program has been removed from the harddisk?
If your system has locate on it, run updatedb and then do a locate httpd and locate apache. That will find everything for ya... I tend to use it because how fast it is due to indexing.
whereis and which httpd come up empty.
The find command also, there is no apache installed anymore on this system.
updatedb and locate report the same, nothing there.
But there it is, in the task monitor, running. I send it a term or kill signal, the processes stop and then immediately spring up again.
I erased the user that the processes are running at, with the only result that now it is running with UID 1006 instead of the user.
This darn processes got nothing, they cannot exist, they cannot get restarted on the system, yet they do. How can I get rid of them without restarting the whole box? Where are these executables launched from?
Is this maybe a sign of a rootkitted system?
Have you looked at /etc/inittab - respawn cmd http://linux.about.com/od/commands/l...l5_inittab.htm. Unusual, but if a dedicated webserver, it may have been set that way.
Also remember that a Unix file doesn't actually get deleted until all processes that have it open have closed it or died. It's just invisible to 'ls/find/whereis' until then.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.