Rajeev,
On Wed, Jun 21, 2000 at 10:09:26AM +0530, Rajeev Jha typed:
> httpd stop is not serving the need , so i went the brute-force way,
> removed the symlink from /etc/rc.d/rc3.d , this works for other
> daemons(like mysql) , but for httpd i also had to remove the httpd
> script file from /etc/rc.d/init.d , just deleting the symlink was not
> working. but what is 'nobody' owning lots of processes ?
>
As you would expect, "httpd stop" stops the httpd daemon temporarily. Next
time you boot, it will get reloaded once again. The number of other httpd
processes that you see are children spawned by httpd daemon in advance to
service any page requests fast. After performing the "httpd stop", you
can issue a "killall httpd" command to kill these processes if you see them
still hanging around.
Don't use the brute-force techniques of removing symlinks from the rcX.d
directories. Use the ntsysv tool (or chkconfig) for setting the services
that start automatically. What these tools do is a little bit more than
simple removal/adding of the required symlinks. If you mess with the
symlinks, you might have problems switching runlevels. (You might have
noticed the mysterious prefixes like K05, S85 etc on these symlinks -
they do have a purpose !)
Kala
-----------------------------------------------------------------------
Check out the 'What to do before posting to the list' site
for a list of things to try before posting. The site is
at http://botsie.tripod.com/beforeposting/
