Using Run Control Scripts

The following procedures show how to use run control scripts to stop or start a legacy service. Also included are instructions for adding or removing a run control script.

Using Run Control Scripts (Task Map)

The following task map includes several procedures that are associated with using run control scripts. Each row includes a task, a description of when you would want to perform that task, followed by a link to the task.

How to Use a Run Control Script to Stop or Start a Legacy Service

1. Become an administrator or assume a role that includes the Service Management rights profile.

   For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

2. Stop the system service.

   # /etc/init.d/filename stop

3. Restart the system service.

   # /etc/init.d/filename start

4. Verify that the service has been stopped or started.

   # pgrep -f service

Example 2-19 Using a Run Control Script to Stop or Start a Service

For example, you can stop the PPPoE server daemon by typing the following:

# /etc/init.d/pppd stop
# pgrep -f nfs

Then, you can restart the PPPoE server daemon by typing the following:

# /etc/init.d/pppd start
# pgrep -f ppp
101748
# pgrep -f ppp -d, | xargs ps -fp
     UID    PID   PPID   C    STIME TTY         TIME CMD
  daemon 101748      1   0   Sep 01 ?           0:06 /usr/lib/inet/pppoed

How to Add a Run Control Script

If you want to add a run control script to start and stop a service, copy the script into the /etc/init.d directory. Then, create links in the rcn .d directory where you want the service to start and stop.

See the README file in each /etc/rc n.d directory for more information on naming run control scripts. The following procedure describes how to add a run control script.

1. Become an administrator or assume a role that includes the Service Management rights profile.

   For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

2. Add the script to the /etc/init.d directory.

   # cp filename/etc/init.d
   # chmod 0744 /etc/init.d/filename
   # chown root:sys /etc/init.d/filename

3. Create links to the appropriate rcn.d directory.

   # cd /etc/init.d
   # ln filename /etc/rc2.d/Snnfilename
   # ln filename /etc/rcn.d/Knnfilename

4. Verify that the script has links in the specified directories.

   # ls /etc/init.d/*filename /etc/rc2.d/*filename /etc/rcn.d/*filename

Example 2-20 Adding a Run Control Script

The following example shows how to add a run control script for the xyz service.

# cp xyz /etc/init.d
# chmod 0744 /etc/init.d/xyz
# chown root:sys /etc/init.d/xyz
# cd /etc/init.d
# ln xyz /etc/rc2.d/S99xyz
# ln xyz /etc/rc0.d/K99xyz
# ls /etc/init.d/*xyz /etc/rc2.d/*xyz /etc/rc0.d/*xyz

How to Disable a Run Control Script

You can disable a run control script by renaming it with an underscore (_) at the beginning of the file name. Files that begin with an underscore or dot are not executed. If you copy a file by adding a suffix to it, both files will be run.

1. Become an administrator or assume a role that includes the Service Management rights profile.

   For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

2. Rename the script by adding an underscore (_) to the beginning of the new file.

   # cd /etc/rcn.d
   # mv filename_filename

3. Verify that the script has been renamed.

   # ls _*
   _filename

Example 2-21 Disabling a Run Control Script

The following example shows how to rename the S99datainit script.

# cd /etc/rc2.d
# mv S99datainit _S99datainit
# ls _*
_S99datainit

How to Convert a Run Control Script to an SMF Service

This procedure shows how to use the advantages of SMF to support an existing run control script. See the svcbundle(1M) man page for more information.

Before You Begin

First, determine which service model the script needs. If the script does some work and then exits without starting any long running processes, it is most likely a transient service. If the script starts up a long running daemon and then exits, then it is a contract service. See the Duration section in the svc.startd(1M) man page for more information about service models.

Next, determine which run level is appropriate for the service. This can be determined by looking at which directory the script is linked into, for example /etc/rc3.d.

1. Become an administrator or assume a role that includes the Service Management rights profile.

   For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

2. Create a temporary manifest.

   In this example, the service name is ex_svc. The is a contract service and runs at level 3.

   # svcbundle -o /tmp/ex_svc.xml -s service-name=ex_svc
         -s start-method=/lib/svc/method/ex_svc -s model=transient

3. Make any additional changes to the manifest.

   Verify that the contents of manifest in /tmp/ex_svc.xml is what you need.

4. Copy the manifest to the correct directory.

   # cp /tmp/ex_svc.xml /lib/svc/manifest/site/ex_svc.xml

5. Stop the existing service.

   # /etc/init.d/ex_svc stop

6. Disable the run control script.

   Remove any links to the run control script from the appropriate rcn.d directories.

7. Import the manifest and start the service.

   # svcadm restart svc:/system/manifest-import