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 the 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 5–1 describes what the check script does.

Table 5–1 What Happens When You
Use the check Script

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, and retains all Bourne shell commands,
variables, and algorithms. Then, check adds the following
comment line at the end:

# version=2 checksum=num

To Validate the custom_probes File

Verify that the check script
is located in the JumpStart directory.

Note –

The check script is in the Solaris_10/Misc/jumpstart_sample directory on the Solaris Operating System DVD or on the Solaris Software - 1 CD.

Change to the JumpStart directory.

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

$ ./check-ppath-rfile_name

-ppath

Validates the custom_probes file by using
the check script from the Solaris software 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 Operating System DVD or Solaris Software - 1 CD.

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

-rfile_name

Specifies a file name other than the one that is named custom_probes. By using the -r option, you can
test the validity of a set of functions before integrating the functions into
the custom_probes file.

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