StarQuest Technical Documents

How to Add the StarLicense for UNIX Daemon to the Boot Process

Last Update: 19 June 2008
Product: StarLicense for UNIX
Version: 1.x
Article ID: SQV00SL003

Abstract

This technical document describes how to add the StarLicense for UNIX daemon to the boot process so that it starts automatically when the operating system starts.

Solution

StarLicense for AIX

StarLicense for FreeBSD

StarLicense for HPUX

StarLicense for Linux

StarLicense for Solaris

StarLicense for AIX

The runtime control (rc) script for StarLicense, /etc/rc.sqlicd, is automatically created when StarLicense is installed.  Use the mkitab command to add an entry to the /etc/inittab file that instructs the operating system to start the StarLicense daemon when the system boots up.

  1. Log on as root user.
  2. Execute the command: /usr/sbin/mkitab 'sqlicd:2:once:/etc/rc.sqlicd start'.
  3. View the contents of the /etc/inittab file to ensure that the entry was added correctly.

StarLicense for FreeBSD

Create a symbolic link in /usr/local/etc/rc.d directory that points to the StarLicense daemon startup script.

  1. Log on as root user.
  2. Run the command:

$ ln -s /usr/share/starlicense/sqlicd.sh /usr/local/etc/rc.d

For FreeBSD v6.1 and later, you can also use this method:
  1. Log on as root user.
  2. Run the command:

    $ ln -s /usr/share/starlicense/100.sqlicd.sh /usr/local/etc/rc.d

  3. Add the following line to /etc/rc.conf to enable `sqlicd'::

    sqlicd_enable="YES"

StarLicense for HPUX

Create symbolic links in the /sbin/rc2.d and /sbin/rc1.d directories pointing to the StarLicense daemon startup and shutdown script.

  1. Log on as root user.
  2. Verify that a symbolic link in /sbin/init.d/sqlicd exists and points to /opt/starlicense/sqlicd.sh. If the link does not exist, create it using the following command:

$ ln -s /opt/starlicense/sqlicd.sh /sbin/init.d/sqlicd

  1. Create two additional symbolic links using the following commands:

$ ln -s /sbin/init.d/sqlicd /sbin/rc2.d/S99sqlicd
$ ln -s /sbin/init.d/sqlicd /sbin/rc1.d/K99sqlicd

The placement of the S99sqlicd symbolic link in the rc2.d directory instructs the operating system to start the StarLicense daemon, using the linked script, when entering level 2 of the startup process, at a priority of 99.

The placement of the K99sqlicd symbolic link in the rc1.d directory instructs the operating system to kill the StarLicense daemon, using the linked script, when entering level 1 of the shutdown process, at a priority level of 99.

StarLicense for Linux

Use the chkconfig command to add the StarLicense daemon to the boot process.

  1. Log on as root user.
  2. Verify that the /etc/init.d/sqlicd symbolic link exists and points to /usr/share/starlicense/sqlicd.sh.
  3. Run the following command to create the necessary links in /etc/rc2.d, etc. (/etc/init.d/rc2.d on SUSE Linux):

$ /sbin/chkconfig --add sqlicd

For Debian Linux, use the update-rc.d to create symbolic links in the /etc/rc2.d, etc directories:

$ update-rc.d sqlicd start 99 2 3 4 5 . stop 99 0 1 6 .

StarLicense for Solaris

Create symbolic links in the /etc/rc2.d and /etc/rc1.d directories pointing to the StarLicense daemon startup and shutdown script.

  1. Log on as root user.
  2. Verify that a symbolic link in /etc/init.d/sqlicd exists and points to /opt/starlicense/sqlicd.sh. If the link does not exist, create it using the following command:

$ ln -s /opt/starlicense/sqlicd.sh /etc/init.d/sqlicd

  1. Create two additional symbolic links using the following commands:

$ ln -s /etc/init.d/sqlicd /etc/rc2.d/S99sqlicd
$ ln -s /etc/init.d/sqlicd /etc/rc1.d/K99sqlicd

The placement of the S99sqlicd symbolic link in the rc2.d directory instructs the operating system to start the StarLicense daemon, using the linked script, when entering level 2 of the startup process, at a priority of 99.

The placement of the K99sqlicd symbolic link in the rc1.d directory instructs the operating system to kill the StarLicense daemon, using the linked script, when entering level 1 of the shutdown process, at a priority level of 99.

DISCLAIMER

The information in technical documents comes without any warranty. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The information in technical documents may be gathered from various sources, including IBM, Microsoft, and other organizations.