Starting the System Resource Controller

Edit online

The System Resource Controller (SRC) is started during system initialization with a record for the /usr/sbin/srcmstr daemon in the /etc/inittab file.

The following are the prerequisites for starting the SRC:

  • Reading and writing the /etc/inittab file requires root user authority.
  • The mkitab command requires root user authority.
  • The srcmstr daemon record must exist in the /etc/inittab file.

The default /etc/inittab file already contains such a record, so this procedure might be unnecessary. You can also start the SRC from the command line, a profile, or a shell script, but there are several reasons for starting it during initialization:

  • Starting the SRC from the /etc/inittab file allows the init command to restart the SRC if it stops for any reason.
  • The SRC is designed to simplify and reduce the amount of operator intervention required to control subsystems. Starting the SRC from any source other than the /etc/inittab file is counterproductive to that goal.
  • The default /etc/inittab file contains a record for starting the print scheduling subsystem (qdaemon) with the startsrc command. Typical installations have other subsystems started with startsrc commands in the /etc/inittab file as well. Because the srcmstr command requires the SRC be running, removing the srcmstr daemon from the /etc/inittab file causes these startsrc commands to fail.
Note: This procedure is necessary only if the /etc/inittab file does not already contain a record for the srcmstr daemon.
  1. Make a record for the srcmstr daemon in the /etc/inittab file using the mkitab command.
    For example, to make a record identical to the one that appears in the default /etc/inittab file, type:
    mkitab -i fbcheck srcmstr:2:respawn:/usr/sbin/srcmstr

    The -i fbcheck flag ensures that the record is inserted before all subsystems records.

  2. Tell the init command to reprocess the /etc/inittab file by typing: 
    telinit q

    When init revisits the /etc/inittab file, it processes the newly entered record for the srcmstr daemon and starts the SRC.