Re: [SLE] apachectl doesn't work Linux/SuSE 7.1

Hi, Sundar. First, I recommend that you check out the README in the /etc/rc.d/ directory on your SuSE 7.1 box. Second, examine the file /etc/rc.d/skeleton and remember that it's precisely that: an example file that you can use to build your own startup scripts off of. Then, read the manpage for insserv. Useful NOW data below... ----- Original Message ----- From: "Sundar @local" To: Sent: Saturday, May 19, 2001 11:03 PM Subject: [SLE] apachectl doesn't work Linux/SuSE 7.1

Hello,

For too many reasons I could not use apache that came with SuSE 7.1, so downloaded from apache.org and successfully built,configured it.

Ok, where did you install your Apache to? Specifically, where are the httpd.pid and the httpd files? You'll need these later.

The problem is I am not able to integrate with system start/stop. I copied the apachectl to /etc/init.d and created symabolic links to rc3.d/rc2.d as S22apachectl/K17apachectl

As I indicated above, you should check out the /etc/rc.d/README and /etc/rc.d/skeleton files and read the insserv manpage.

I used the same method in my Solaris box, it works. What's different in Linux

More specfically, "What's different in SuSE 7.1 Linux" is the question you should be asking. Answer: SuSE 7.1 follows the Linux Standards Base rather much.

Any help is deeply appreciated

Check out the listing below....

Regards,Sundar

...

...

...

...

...

> Edit the text below to match your config, specifically the locateuon for httpd and the httpd.pid files. Then paste it into a file in /etc/rc.d (I suggest apache) and make sure that your /etc/rc.config file has START_APACHE="yes" somewhere in it, uncommented. (you might want to read

HTH! Geordon the rest of that file, too, while you're there) Then run insserv. Also you might want to "ln -s /etc/init.d/apache /usr/sbin/rcapache" and "chmod +x /etc/init.d/apache" Good luck. This is what I did to my system and it works fine.

...

...

...

...

...

>>CUT HERE<<<<<<<<<< #! /bin/sh # # Author: Geordon VanTassle # # init.d/apache # # and symbolic its link # # /sbin/rcapache # # System startup script for the nessus backend nessusd # ### BEGIN INIT INFO # Provides: apache # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start Apache. ### END INIT INFO

# Source SuSE config . /etc/rc.config # Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]} # Force execution if not called by a runlevel directory. test $link = $base && START_APACHE=yes test "$START_APACHE" = yes || exit 0 APACHE_BIN=/opt/apache/bin/httpd test -x $APACHE_BIN || exit 5 # Shell functions sourced from /etc/rc.status: # rc_check check and set local and overall rc status # rc_status check and set local and overall rc status # rc_status -v ditto but be verbose in local rc status # rc_status -v -r ditto and clear the local rc status # rc_failed set local and overall rc status to failed # rc_reset clear local rc status (overall remains) # rc_exit exit appropriate to overall rc status . /etc/rc.status # First reset status of this service rc_reset # Return values acc. to LSB for all commands but status: # 0 - success # 1 - misc error # 2 - invalid or excess args # 3 - unimplemented feature (e.g. reload) # 4 - insufficient privilege # 5 - program not installed # 6 - program not configured # 7 - program is not running # # Note that starting an already running service, stopping # or restarting a not-running service as well as the restart # with force-reload (in case signalling is not supported) are # considered a success. case "$1" in start) echo -n "Starting Apache" ## Start daemon with startproc(8). If this fails ## the echo return value is set appropriate. # startproc should return 0, even if service is # already running to match LSB spec. startproc $APACHE_BIN # Remember status and be verbose rc_status -v ;; stop) echo -n "Shutting down Apache" ## Stop daemon with killproc(8) and if this fails ## set echo the echo return value. killproc -TERM $APACHE_BIN # Remember status and be verbose rc_status -v ;; try-restart) ## Stop the service and if this succeeds (i.e. the ## service was running before), start it again. $0 stop && $0 start # Remember status and be quiet rc_status ;; restart) ## Stop the service and regardless of whether it was ## running or not, start it again. $0 stop $0 start # Remember status and be quiet rc_status ;; force-reload) ## Signal the daemon to reload its config. Most daemons ## do this on signal 1 (SIGHUP). ## If it does not support it, restart. echo -n "Reload service Apache" ## if it supports it: killproc -HUP $APACHE_BIN #touch /opt/apache/logs/httpd.pid rc_status -v ## Otherwise: #$0 stop && $0 start #rc_status ;; reload) ## Like force-reload, but if daemon does not support ## signalling, do nothing (!) # If it supports signalling: echo -n "Reload service Apache" killproc -HUP $APACHE_BIN #touch /opt/apache/logs/httpd.pid rc_status -v # If it does not support reload: #exit 3 ;; status) echo -n "Checking for Apache: " ## Check status with checkproc(8), if process is running ## checkproc will return with exit status 0. # Status has a slightly different for the status command: # 0 - service running # 1 - service dead, but /var/run/ pid file exists # 2 - service dead, but /var/lock/ lock file exists # 3 - service not running # If checkproc would return LSB compliant ret values, # things could be a little bit easier here. This will # probably soon be the case ... checkproc $APACHE_BIN; rc=$? if test $rc = 0; then echo "OK" else echo "No process" if test -e /opt/apache/logs/httpd.pid; then exit 1 else exit 3 fi fi #rc_status ;; probe) ## Optional: Probe for the necessity of a reload, ## give out the argument which is required for a reload. test /opt/apache/conf/httpd.conf -nt /opt/apache/logs/httpd.pid && echo reload ;; *) echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}" exit 1 ;; esac rc_exit