HP Visualize J210XC IRIX to HP-UX Migration Guide - Page 12
K480syncer
View all HP Visualize J210XC manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 12 highlights
System Startup and Shutdown 2 Script was skipped due to overriding control variables from /etc/rc.config.d files or for other reasons and did not actually do anything. Causes the status N/A to appear in the checklist. 3 (Reserved for key system components.) Script executed normally and requires an immediate system reboot for the changes to take effect . Configuration Variable Scripts Configuration variable scripts are designed to customize the execution scripts. The goal here is to separate startup files from configuration files so that upgrading your system does not overwrite its configuration. These scripts are written for the POSIX shell (/usr/bin/sh or /sbin/sh), and not the Bourne shell (ksh, or csh). In some cases, these files must also be read, and possibly modified, by other scripts or the SAM program. For this reason, each variable definition must appear on a separate line, in the syntax: variable=value No trailing comments may appear on a variable definition line. Comment statements must be on separate lines, with the # comment character in column 1. An example of the required syntax for configuration files is given below: # Cron configuration. See cron(1m) # # CRON: Set to 1 to start cron daemon # CRON=1 Both the execution scripts and the configuration files are named after the subsystem they control. For example, the /sbin/init.d/cron execution script controls the cron daemon, and it is customized by the /etc/rc.config.d/cron configuration variable script. Link Files These files control the order in which execution scripts run. The /sbin/rc#.d (where # is a run-level) directories are startup and shutdown sequencer directories. They contain only symbolic links to the execution scripts in /sbin/init.d, which are executed by /sbin/rc on transition to a specific run level. For example, the /sbin/rc3.d directory contains symbolic links to scripts that are executed when entering run level 3. These directories contain two types of link files: start links and kill links. Start links have names beginning with the capital letter S and are invoked with the start argument at system boot time or on transition to a higher run level. Kill links have names beginning with the capital letter K and are invoked with the stop argument at system shutdown time or when moving to a lower run level. Further, all link files in a sequencer directory are numbered to ensure a particular execution sequence. Each script has, as part of its name, a three-digit sequence number. This, in combination with the start and kill notation, provides all the information necessary to properly start up and shut down a system. The table below shows some samples from the run-level directories. (The sequence numbers shown are only examples and may not accurately represent your system.) /sbin/rc0.d K480syncer K800killall K900hfsmount /sbin/rc1.d S100hfsmount S320hostname S440savecore S500swapstart S520syncer K270cron K280lp K390rbootd K460sendmail /sbin/rc2.d S340net S500inetd S540sendmail S610rbootd S720lp S730cron K900nfs.server /sbin/rc3.d S000nfs.server 7