Problem
Intending to give a non-root user system backup capabilities, I added "backup" and "sysadmin" authorizations for that user with the Account Manager. However, the user gets the error:
Failed to retrieve local filesystem list for host <hostname>
when trying to launch the Backup Manager. Details for this
error say "The lock file /etc/sysadm.d/lib/filesystemlock doesn't
exist or is not writable. Cannot obtain filesystemlock."
However, the file does exist. Cause
The user needs to be added to the backup and sysadmin groups. Also, the permissions and group on the file /etc/sysadm.d/lib/filesystemlock need to be changed.
Solution
First, make sure that the user is in the appropriate groups and
has the correct authorizations. They should have backup and
sysadmin authorizations, and be in the backup and sysadmin
groups.To do this, launch the Account Manager, and highlight the user.
Choose User from the Menu, and then choose Modify. Then select
Change Group Membership. If the backup and sysadmin groups are
not included for the user, add them. To make sure of their
authorizations, again select User from the Menu (with the user
still highlighted). Choose Authorizations from the pull-down
menu. If the user does not have backup and sysadmin authorizations,
then add these to the user's profile.The user must be able to write to the file:
/etc/sysadm.d/lib/filesystemlockin order to access the Backup Manager, but the permissions on
that file allow only the root user to modify the file. Also,
the file may have incorrect group attributes, which would affect
the ability of the sysadmin group - of which the user in question
is now a member - to write to the file.Since /etc/sysadm.d/lib/filesystemlock is a linked file, the most
reliable solution to these problems with its attributes is to
remove the link, correct the attributes of the file to which it
links, and restore the link. To do this, follow these steps:1. # rm /etc/sysadm.d/lib/filesystemlock2. # cd /var/opt/K/SCO/Unix/5.0.5Eb/sa/filesystem3. # touch lock (if a listing shows no file of this name)
# chgrp sysadmin lock# chmod 664 lock4. ln -s -f lock /etc/sysadm.d/lib/filesystemlockAt the end of this procedure, the files should appear as follows:
# l /etc/sysadm.d/lib/filesystemlock-rw-rw-r-- 1 root sysadmin 0 Sep 29 1998 /etc/sysadm.d/lib/filesystemlock@# ls -l /etc/sysadm.d/lib/filesystemlocklrwxrwxrwx 1 root sys 46 Oct 29 15:57
/etc/sysadm.d/lib/filesystemlock ->
/var/opt/K/SCO/Unix/5.0.5Eb/sa/filesystem/lock# l /var/opt/K/SCO/Unix/5.0.5Eb/sa/filesystem/lock-rw-rw-r-- 1 root sysadmin 0 Sep 29 1998 /var/opt/K/SCO/Unix/5.0.5E
b/sa/filesystem/lockWith these attributes for the two files, the user should be able to access the Backup Manager.
This problem is scheduled to be addressed in a future release of SCO OpenServer 5.
See also
ta109576, "Backup Manager fails to save options under SCO OpenServer 5.0.4 and 5.0.5."
ta109348, "The 5.0.4 and 5.0.5 SCOadmin Backup Manager restore selection buttons don't work."
Manual page backup(ADM)