>Well I guess you need to go through your scripts and find out what exactly is starting webservd.

i did not make any scripts my-self. it was the webserver doing itself . its starting automatically as soon as system stats up.

hrere is the all files inside /etc/rc.d/init.d folder



anacron firstboot isdn network portmap single winbind
apmd functions kdcrotate nfs random snmpd xfs
atd gpm keytable nfslock rawdevices snmptrapd xinetd
autofs halt killall nscd rhnsd sshd ypbind
crond iptables kudzu ntpd saslauthd syslog
cups irda netfs pcmcia sendmail webserver01

here is the scripts inside webserver01


#!/bin/sh
#------------------------------------------------------------------------------
# Generated for the Sun ONE Web Server 6.1
#
# Author: Sun Microsystems, Inc. (2003)
#------------------------------------------------------------------------------

# Source function library.
. /etc/rc.d/init.d/functions

SCRIPT_NAME=webserver01
S1WS_HOME=/opt/SUNWwbsvr
S1WS_VERSION="6.1"

# See how we were called.
case "$1" in
start)
echo "Sun ONE Web Server $S1WS_VERSION starting ($S1WS_HOME)"
for each_server in $S1WS_HOME/https-*
do
if [ -d $each_server ]; then
echo -n " `basename $each_server`: "
$each_server/start && success || failure $1
echo
fi
done
touch /var/lock/subsys/$SCRIPT_NAME > /dev/null 2>&1
;;
stop)
echo "Sun ONE Web Server $S1WS_VERSION stopping ($S1WS_HOME)"
for each_server in $S1WS_HOME/https-*
do
reversed_list="$each_server $reversed_list"
done
for each_server in $reversed_list
do
if [ -d $each_server ]; then
echo -n " `basename $each_server`: "
$each_server/stop 2>&1 && success || failure $1
echo
fi
done
rm -f /var/lock/subsys/$SCRIPT_NAME > /dev/null 2>&1
;;
restart)
$0 stop || return=$rc_failed
$0 start || return=$rc_failed
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit 0

SHOULD I DELETE THIS SCRIPT FROM THE SYSTEM ? will it be harmful ?

any response please.

How about "/etc/rc.d/init.d/webserver01 stop" (no quotes) followed by "chkconfig webserver01 off".

Oh, and constantly bumping your own post is annoying and makes people less likely to want to help you. Posters here tend to be busy folks who can't necessarily help you immediately.

many , you are a e geneious . this works immediately. this command has worked.

here is the output from the shell


# /etc/rc.d/init.d/webserver01 stop
Sun ONE Web Server 6.1 stopping (/opt/SUNWwbsvr)
https-mach104: server has been shutdown
[ OK ]
https-admserv: server has been shutdown
[ OK ]


yahooooooooo......its done.



BTW, is this permanently stopped ?? or again it will start automaticall as soon as i start my system again ? what do you think ?....i am not shutting down system right now though.

It is not permanently stopped, you just shut it off for your current session. You should try the second part of the suggested command, where you were wisely told to try by btmiller. Try that, and see what it does. Also, if you are actually using this machine, please upgrade to a distro from the 21st century. RedHat 9 is ancient, unsupported junk. It is like finding a newspaper from 6 years ago. Kind of interesting to look at, but of no practical use at all. How everyone and their grandmother installed (and continues to install) that distro is beyond me. I did it at one point as well, it was my first linux. If you like redhat, try fedora core 4. If you don't like it, there are hundreds of other choices, all of them current releases.

Peace,
JimBass

followed by "chkconfig webserver01 off".

i did this sir...but NO success.

here is the output from the shell
# chkconfig webserver01 off
service webserver01 does not support chkconfig

that means it has not been disabled yet ?

anybody please suggest something .

any linux guru ?

nobody knows .

plese tell me if you want some more information

There are three places where a daemon like this might be started:

1. Directly in /etc/inittab.
2. Via a symbolic-link starting with the letter "S" somewhere in, say, /etc/rc.d/rc5.d.
3. By means of the xinetd daemon, say with a file in /etc/xinetd.d.

If a process is continuously pegging the system at 100% busy, then that program is probably looping (malfunctioning). It usually puts some kind of message in a file in the /var/log directory when it does so.

ok, but how do i fix it ? webserver is starting as soon as system starts up. the webserver is perfectly alright and it is functioning well.

ALL I need is to stop it running from the system start up.