24.12.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

APPENDIX B<br />

FILE DAEMON<br />

The File Daemon provides extended file protection. The File Daemon<br />

described in this appendix is a prototype that you may use to help you<br />

in understanding the monitor support for this feature. The File<br />

Daemon is supplied only to serve as a prototype for the File Daemon<br />

you may desire at your installation.<br />

Each installation will have varying types of accounting and file<br />

security measures. Therefore, each installation's File Daemon may be<br />

written to account for these differences and varying requirements.<br />

The DIGITAL-supplied, prototype File Daemon supports access lists and<br />

access logging that is performed on a user's or a system<br />

administrator's request.<br />

B.l USER INTERFACE<br />

The File Daemon allows any user to specify who can and who cannot<br />

access his files. Each user may create a file named ACCESS.USR (which<br />

is described in Section C.3). This file optionally lists the names of<br />

some or all of that user's files and specifies, on an individual file<br />

basis, the users who can and cannot access those files. Under<br />

specific conditions, the File Daemon examines the user's ACCESS.USR<br />

file and may record information, in a separate file called ACCESS.LOG,<br />

regarding specific access requests to the listed files. Note that<br />

ACCESS.USR can be created only by the owner of the particular<br />

directory or by a job logged in under [1,2].<br />

B.2 THE FILE DAEMON<br />

The monitor calls the File Daemon (only if the monitor feature<br />

switch F%FDAE = -1) each time that someone tries to·access a file<br />

has a 4, 5, 6, or 7 protection code in the owner's protection<br />

field and the access fails due to a file protection error or due<br />

directory protection error.<br />

test<br />

that<br />

code<br />

to a<br />

For example, if you protect a file against a specific user and that<br />

user attempts to access your file (with a LOOKUP, ENTER, RENAME, or<br />

FILOP. monitor call), the monitor suspends the execution of the<br />

accessing user's program and it sends a message to the File Daemon.<br />

This message includes the type of access the user is attempting and<br />

that user's project-programmer number. The monitor gives control to<br />

the File Daemon, which looks for your file called ACCESS.USR.<br />

ACCESS.USR must be on the same file structure and in the same<br />

directory area as the file being accessed.<br />

B-1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!