test

Solaris 8 Advanced Installation Guide

Validating the custom_probes File

Before you can use a profile, rules, and custom_probes file, you must run the check script to validate that these files are set up correctly. If all profiles, rules, and probe and comparison functions are correctly set up, the rules.ok and custom_probes.ok files are created. Table 20–3 describes what the check script does.

Table 20–3 What Happens When You Use check

Stage 

Description 

1 

check searches for a custom_probes file.

2 

If the file exists, check creates the custom_probes.ok file from the custom_probes file, removes all comments and blank lines, retains all Bourne shell commands, variables, and algorithms, and adds the following comment line at the end:

# version=2 checksum=num

Note –

Ensure that root owns the custom_probes.ok file and that its permissions are set to 755.

Syntax of check

This is the syntax of the check script you use to test a custom_probes file:


$ ./check [[-p path -r file_name]]

Table 20–4 Description of check Script Arguments

Argument 

Description 

-p path

Validates the custom_probes file by using the check script from the Solaris 8 Software 1 of 2 CD image for your platform, instead of the check script from the system you are using. path is the image on a local disk or a mounted Solaris 8 Software 1 of 2 CD.

Use this option to run the most recent version of check if your system is running a previous version of Solaris.

-r file_name

Specifies a file name other than the one named custom_probes. Using this option, you can test the validity of a set of functions before integrating it into the custom_probes file.

To Validate the custom_probes File

  1. Make sure the check script is located in the JumpStart directory.

    Note –

    The check script is in the Solaris_8/Misc/jumpstart_sample directory on the Solaris 8 Software 1 of 2 SPARC Platform Edition and Solaris 8 Software 1 of 2 Intel Platform Edition CD.

  2. Change to the JumpStart directory.

  3. Run the check script to validate the rules and custom_probes files. 


    $ ./check [[-p path -r file_name]]

    As the check script runs, it reports the validity of the rules and custom_probes files and each profile. If no errors are encountered, it reports: “The custom JumpStart configuration is ok” and creates the rules.ok and custom_probes.ok files in the JumpStart directory.

  4. Is the custom_probes.ok file executable?

    • If yes, stop, you're done.

    • If no, type the command:

      chmod +x custom_probes