TOPS-10 Monitor Calls Manual Volume 2 AA-K039D ... - Trailing-Edge

FILE DAEMON
3. If the file's owner protection code field is such that the
File Daemon is called and the owner has neglected to include
his own project-programmer number in ACCESS.USR for this
file, the File Daemon grants the owner the same type of
access as if a 7 were in the owner's protection code field
(that is, the owner can only read the file or change the
file's protection code.)
4.
ACCESS.USR files may be restored at
Therefore, operators should not perform a
disk using BACKUP when the File Daemon is
full restore is done, the action may
restore files that ACCESS.USR allows them
arbitrary times.
full restore of the
running. If such a
not allow BACKUP to
to BACKUP.
5. The CHKACC monitor call tells a program what a user's file
access privileges are. Therefore, by using CHKACC, a program
can tell if the File Daemon will be called, but it will not
know the access privileges returned by the File Daemon.
B.3 ACCESS.USR
Every user can create his own ACCESS.USR file. Note that ACCESS.USR
files can be created only by the owner of the specific directory or a
[1,2] job. ACCESS.USR is made up of one or more 'command lines'. You
must write each command line in the following format:
file-spec/switches=[ppn]/switches, ... , [ppn]/switches
The file-spec is a full file specification (that is, device:
filename.extension [path]). The File Daemon scans each line in
ACCESS.USR until it matches a file specification on the left of the
equal sign and a project-programmer number on the right. All access
rights will then be determined by that line (there will be no
continued scan). The user should minimally specify one of the
switches synonymous with protection codes (such as, READ, EXECUTE,
ALL, ... ) for that file specification; refer to Table C-1. If you do
not specify a switch, a default of /NONE is provided. The possible
switches are listed in Table C-1.
B-3