ASET Error Messages

This section documents the error messages generated by ASET.

ASET failed: no mail program found.

ASET is directed to send the execution log to a user, but no mail program can be found. To fix the problem, install a mail program.

USAGE: aset [n user[@host]] in /bin mail or /usr/ucb/mail
Cannot decide current and previous security levels.

ASET cannot determine what the security levels are for the current and previous invocations. To fix the problem, ensure the current security level is set either through the command line option or by using the ASETSECLEVEL environment variable from a shell. Also, ensure that the last line of the ASETDIR/archives/asetseclevel.arch file correctly reflects the previous security level. If these values are not set or are incorrect, specify them correctly.

ASET working directory undefined.
To specify, set ASETDIR environment variable or use command line option -d
ASET startup unsuccessful.

The ASET working directory is not defined or is defined incorrectly. To fix the problem, use the ASETDIR environment variable or the -d command line option to correctly specify the ASET working directory and restart ASET.

ASET working directory $ASETDIR missing.
ASET startup unsuccessful.

The ASET working directory is not defined or it is defined incorrectly. This may be because the ASETDIR variable refers to a nonexistent directory. Ensure that the correct directory--the directory containing the ASET directory hierarchy--is referred to correctly.

Cannot expand $ASETDIR to full pathname.

ASET cannot expand the directory name given by the ASETDIR variable or the -d command line option to a full path name. To fix the problem, ensure that the directory name is correct and that it refers to an existing directory to which the user has access.

aset: invalid/undefined security level.
To specify, set ASESTSECLEVEL environment variable or use command line
option -l, with argument= low/med/high.

The security level is not defined or it is defined incorrectly. Only the values low, med, or high are acceptable. To fix the problem, use the ASETSECLEVEL variable or the -l command line option to specify one of the three values.

ASET environment file asetenv not found in $ASAETDIR.
ASET startup unsuccessful.

ASET cannot locate an asetenv file in its working directory. To fix the problem, ensure that there is an asetenv file in ASET's working directory.

<filename> doesn't exist or is not readable.

The file referred to by <filename> doesn't exist or is not readable. This problem can occur when using the -u option in which you can specify a file that contains a list of users whom you want to check. To fix the problem, ensure the argument to the -u option exists and is readable.

ASET task list TASKLIST undefined.

The ASET task list, which should be defined in the asetenv file, is not defined. Your asetenv file may be bad, or the entry may be missing. To fix the problem, examine your asetenv file. Ensure the task list is defined in the User Configurable section. Also check other parts of the file to ensure the file is intact. Refer to the asetenv(4) manual page for the content of a good asetenv file.

ASET task list TASKLIST missing.
ASET startup unsuccessful.

The ASET task list, which should be defined in the asetenv file, is not defined. Your asetenv file may be bad, or the entry may be missing. To fix the problem, check the User Configurable section of the asetenv file to ensure the variable is defined as in the proper format.

Warning! Duplicate ASET execution scheduled.
Check crontab file.

ASET is scheduled more than once. In other words, scheduling is requested while a schedule is already in effect. This conflict may not necessarily be an error if more than one schedule is desired. If you want more than one schedule, you should use crontab(1) scheduling. To fix the problem, check your crontab file to make sure that the correct schedule is in effect and that no duplicate crontab entries for ASET exist.