Legacy startup script procedure

p { margin-bottom: 0.08in; }

This procedure is commonly used on System 5 implementations such as SOLARIS, HPUX, AIX, LINUX.

Although this setup procedure will work on all Unix systems, care should be taken as to ascertain the native startup scheme for the OS you are working with. Usually the OS has a native interface to that aspect of it’s infrastructure :

HPUX = SAM
AIX = SMITH
SOLARIS = SVC
LINUX = Determined by choice of flavour and support applications.

In this exercise, we are using the OS independent Berkely setup. This setup uses the:

Script depository directory /etc/init.d
The startup shutdown hierarchy directrories /etc/rc.d/rc#.d

For illustration purposes, we will use a common feature application such as httpd.

Here is an example of the httpd startup script (see addenda 1) that is usually installed in the /etc/init.d directory when the webserver is installed. Sometimes, that startup scritp may be installed directly in the application directories. A link to the application startup script should be done from there if needed.

Notice that the script has several parameters that are usually “start, stop, restart, status, other…” this is common for a startup script. Should you execute the command line :
/etc/init.d/httpd stop
this would effectively tell the script to execute the code that would stop the current running httpd daemon and the access to the port 80 or other implied would cease.
/etc/init.d/httpd start
would restart it.

System 5 implementation use the rc and rc.sysinit system startup scripts that will read the /etc/rc.d directory hierarchy and locate links that have the forme of :
/etc/rc.d/rc3.d/S85httpd -> ../init.d/httpd and /etc/rc.d/rc3.d/K85httpd -> ../init.d/httpd

Notice the S and K at the beginning of the link and the 85 after it.
The S entry in the rc3.d directory is there to tell the system to Start at sequence number 85 the script /etc/init.d/httpd after all other scripts in other rc2.d, rc1.d, rc0.d have been executed. The number 85 is arbitrary to the rc#.d directory and tells the rc script to start that numbered script after the lower numbers in that directory have been dealt with. A K entry would tell the system to kill the process and all other processes associated according to the code in the startup script in the same manner.

So to startup the httpd daemon at system boot you would do this :

1. Install httpd as per instruction.

2. Make sure that the startup script “httpd” is present, available and executable, should have “ -rwxr-xr-x ” permissions 0755 with user root and group root.

3. Copy the httpd script in the /etc/init.d directory if not already there.

4. Execute the command find /etc -name “*http*” –ls to make sure that the S or K entries do not already exist.

5. Cd to /etc/rc.d/rc3.d

6. Use the command ln –s /etc/init.d/httpd S85httpd

7. It is wise to add a –s /etc/init.d/httpd K##httpd with a smaller number that the startup sequence to make sure that all associated files and dependencies are closed or stopped before starting a process.

8. At reboot, the system will start httpd after all preceding processes are done.

 

p { margin-bottom: 0.08in; }

Httpd startup script

#!/bin/sh # # Startup script for the Apache Web Server # # chkconfig: - 85 15 # description: Apache is a World Wide Web server. It is used to serve / # HTML files and CGI. # processname: httpd # pidfile: /usr/local/apache/logs/httpd.pid # config: /usr/local/apache/conf/httpd.conf ulimit -n 1024 ulimit -n 4096 ulimit -n 8192 ulimit -n 16384 # # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # # # Apache control script designed to allow an easy command line interface # to controlling Apache. Written by Marc Slemko, 1997/08/23 # # The exit codes returned are: # XXX this doc is no longer correct now that the interesting # XXX functions are handled by httpd # 0 - operation completed successfully # 1 - # 2 - usage error # 3 - httpd could not be started # 4 - httpd could not be stopped # 5 - httpd could not be started during a restart # 6 - httpd could not be restarted during a restart # 7 - httpd could not be restarted during a graceful restart # 8 - configuration syntax error # # When multiple arguments are given, only the error from the _last_ # one is reported. Run "apachectl help" for usage info # ARGV="$@" # # |||||||||||||||||||| START CONFIGURATION SECTION |||||||||||||||||||| # -------------------- -------------------- # # the path to your httpd binary, including options if necessary if [ -e "/etc/chroothttpd" ]; then HTTPD=/usr/local/cpanel/bin/chroothttpd else HTTPD=/usr/local/apache/bin/httpd fi # # pick up any necessary environment variables if test -f /usr/local/apache/bin/envvars; then . /usr/local/apache/bin/envvars fi # # a command that outputs a formatted text version of the HTML at the # url given on the command line. Designed for lynx, however other # programs may work. LYNX="lynx -dump" # # the URL to your server's mod_status status page. If you do not # have one, then status and fullstatus will not work. PORT="$(grep 'apache_port=' /var/cpanel/cpanel.config 2>/dev/null | sed -e 's/.*=/([.0-9]*:/)/{0,1/}//;' - e 's/[^0-9]*//g' 2>/dev/null)" STATUSURL=http://localhost:${PORT:-80}/whm-server-status # # Set this variable to a command that increases the maximum # number of file descriptors allowed per child process. This is # critical for configurations that use many file descriptors, # such as mass vhosting, or a multithreaded server. ULIMIT_MAX_FILES="ulimit -S -n `ulimit -H -n`" # -------------------- -------------------- # |||||||||||||||||||| END CONFIGURATION SECTION |||||||||||||||||||| # Set the maximum number of file descriptors allowed per child process. if [ "x$ULIMIT_MAX_FILES" != "x" ] ; then $ULIMIT_MAX_FILES fi ERROR=0 if [ "x$ARGV" = "x" ] ; then ARGV="-h" fi case $ARGV in start|stop|restart|graceful) $HTTPD -k $ARGV -DSSL ERROR=$? ;; startssl|sslstart|start-SSL) $HTTPD -k start -DSSL ERROR=$? ;; configtest) $HTTPD -t ERROR=$? ;; status) $LYNX $STATUSURL | awk ' /process$/ { print; exit } { print } ' ;; fullstatus) $LYNX $STATUSURL ;; *) $HTTPD $ARGV ERROR=$? esac exit $ERROR