End of support for EZproxy on Solaris platform
OCLC ended support for EZproxy on the Solaris 10 (x86) platform on October 31, 2018. We no longer provide software for this platform. We will continue to provide Linux and Windows versions of the software. Customers using EZproxy on Solaris should plan to move their installation of EZproxy to Linux or Windows. If you have questions about this change, please reach out to Customer Support (firstname.lastname@example.org).
If you are running a Linux or Solaris version of EZproxy, UMask allows you to manually control who is able to access EZproxy files.
UMask is a position-independent directive that provides a numeric value that controls the permissions on fields created by the Linux and Solaris versions of EZproxy. This directive serves no meaningful purpose on Windows.
The syntax of this directive is the same as the Linux and Solaris command umask. When UMask is not specified, its default value is 0077, which limits access on files to the account that is used to run EZproxy. Refer to the table below for information on computing the values for use with UMask.
Qualifier Description mode A four-digit number that must start with 0 and is followed by three other digits. The digits are calculated by adding together the permissions that should not be granted, using 4 for read, 2 for write, and 1 for execute. The second digit controls user access, the third digit controls group access, and the fourth digit controls access for all others. The default value is 0077, where the first 0 is the required value, the second 0 indicates that user access should not be restricted, the third 7 indicates that all group access should be denied, and the fourth 7 indicates that access for all others should be denied.
- If you want to provide read only access on your Linux server, you could enter the following statements in your config.txt.
UMask 0037This would allow users to read, write, and execute; groups to read, but not write or execute; and all others no permissions.
- Related directives