Fitzgerald & Long Sentry, User Manual

Page: 27 / 113

SENTRY User’s Guide Section 1 - 9
Fitzgerald & Long
3
. “Password for User XXXXX is less than N characters.”
- The user “XXXXX” has a
password which is shorter than the minimum password length specified in the SENTRY System Profile
screen, which is
N . This user’s password should be updated to conform to the minimum length restrictions
you have instituted.
4.
“User XXXXX has no home directory.” - The user “XXXXX” has no home directory specified.
This would prevent the user from logging in, as UNIX would not know where to attach the user upon login.
The user should be updated and assigned a home directory.
5.
“User XXXXX has an invalid home directory - /ZZZZZ.”
- The user “XXXXX” has a home
directory in the SENTRY database of “/ZZZZZ”, but SENTRY cannot locate this directory on your file
system. Perhaps the directory was removed after it was assigned as the user’s home directory. The user
should be updated and assigned a valid home directory.
6.
“Group XXXXX is not on the SENTRY.GROUPS file.” - A Group name was found in
SENTRY’s control list which does not exist in the SENTRY.GROUPS file. This indicates that one of
SENTRY’s database files is damaged and should be rebuilt. Upload the passwd and group files to fix this
problem.
7.
“Command XXXXX not on the SENTRY.COMMANDS file.”
- A VOC protection item was
found in SENTRY’s control list which does not exist in the SENTRY.COMMANDS file. This indicates
that one of SENTRY’s database files is damaged and should be rebuilt.
Errors beginning with the word “Warning” are informational - not serious database issues but situations
you should be aware of. The following is a list of those warnings.
1.
“User XXXXX will default to “other” protection on all objects and commands.”
- The
user “XXXXX” is not specifically mentioned, either by user ID or group membership, in the permissions
for any file system object or any VOC command protected by SENTRY. He will fall into the “other”
category for all protection on the system. This is NOT a problem, but could serve as an indication of a
user ID which is obsolete and no longer used.
2.
“Group XXXXX is not used by any user.”
- The group “XXXXX” is not being used by any user
on the system. Therefore, no users will receive their access permissions via this group. This may be a
group which is obsolete and should be removed or renamed.
3.
“Group XXXXX is not used to protect any object or command.” - The group “XXXXX” is
not referenced in the permissions for any disk object or any VOC command. It may be assigned to users,
but is not used to protect anything. This might be an obsolete group which should be removed or renamed.
4.
“Owner (UID) XXXXX on /ZZZZZ does not exist.”
- The user ID number “XXXXX” is the
owner of a disk object whose path is “/ZZZZZ”. However, there is no user who is assigned this user ID
number. Possibly, there once was a user but he has been deleted. The owner for this disk object should be
replaced with a valid user on the system. Alternatively, a new or existing user could be assigned the same
user ID number (UID).