World Map
Java Service Wrapper is the easiest way to make your product more reliable.
  • Free Trial
  • Buy Now
wrapper.umask Property

Index

wrapper.umask

Compatibility :3.2.0
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM z/Linux

Sets the permission used when creating files. The "umask" is used to DISABLE certain permission bits for files. Values can be entered in decimal or hexadecimal or octal formats. The default value is the umask of the process launched the Wrapper. (Please note, until Wrapper version 3.5.7, the default umask was fixed to "0022", which is an octal number.)

Values beginning with '0x' will be treated as hexadecimal (base 16). The leading '0' causes the number to be parsed as octal (base 8) otherwise it is treated as a decimal (base 10) number,

Target:

In octal format the umask is defined as a 4 digit number (0/rwx/rwx/rwx) starting with a "0" (zero).

  • The first, left-most except the initial "0" (zero),
  • digit specifies the blocked permissions for the owner user creating the file.
  • The second digit specifies the blocked permissions for other users who are members of the file's group.
  • The third, right-most, digit specifies the blocked permissions for any other users.

Access Restriction:

Each digit is specified by adding up the following values:

  • 4: to restrict read access (r),
  • 2: to restrict write access (w),
  • 1: to restrict executable access (x).

Example:

A value of "7" (=4+2+1) blocks the access of read(4), write(2) and execute(1). For example, "000" gives widely openly permission to everyone. "077" gives full-access permission to only owner user.

For instance, the umask of "0022" will restrict all users except the creator from writing or modifying files. To prevent other users from being able to execute or even see the files, the restriction "077" is required; therefore, the umask value of "0077" should be used.

Example:
wrapper.umask=0022

wrapper.*.umask

Compatibility :3.2.0
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM z/Linux

The Wrapper also makes it possible to specify the umask for particular files created by the Wrapper by using the following properties. Each defaults to the value of the wrapper.umask property.

  • wrapper.umask :

    Specifies the default umask and umask of the Wrapper process.

  • wrapper.anchorfile.umask :

    Specifies the umask to use when creating the anchor file. See the wrapper.anchorfile property.

  • wrapper.lockfile.umask :

    Specifies the umask to use when creating the lock file. See the wrapper.lockfile property.

  • wrapper.pidfile.umask :

    Specifies the umask to use when creating the pid file. See the wrapper.pidfile property.

  • wrapper.statusfile.umask :

    Specifies the umask to use when creating the status file. See the wrapper.statusfile property.

  • wrapper.java.umask :

    Specifies the default umask of the Java process, and thus of any files created by the Java application.

  • wrapper.java.idfile.umask :

    Specifies the umask to use when creating the Java id file. See the wrapper.java.idfile property.

  • wrapper.java.pidfile.umask :

    Specifies the umask to use when creating the Java pid file. See the wrapper.java.pidfile property.

  • wrapper.java.statusfile.umask :

    Specifies the umask to use when creating the Java status file. See the wrapper.java.statusfile property.

  • wrapper.logfile.umask :

    Specifies the umask to use when creating the log file. See the wrapper.logfile property.

Reference: logfile