CHMOD 700 – coolinarism
post-template-default,single,single-post,postid-13493,single-format-standard,eltd-core-1.1.1,symple-shortcodes ,symple-shortcodes-responsive,flow-ver-1.3.7,,eltd-smooth-page-transitions,ajax,eltd-blog-installed,page-template-blog-standard,eltd-header-standard,eltd-fixed-on-scroll,eltd-default-mobile-header,eltd-sticky-up-mobile-header,eltd-dropdown-default,wpb-js-composer js-comp-ver-6.0.5,vc_responsive



In computing, umask is a command that determines the settings of a mask that controls how file permissions are set for newly created files. It also may refer to a function that sets the mask, or it may refer to the mask itself, which is formally known as the file mode creation mask. The mask is a grouping of bits, each of which restricts how its corresponding permission is set for newly created files. The bits in the mask may be changed by invoking the umask command.
the truth table for the masking logic. Each bit in the requesting process’ file permission mode is operated on by the mask using
this logic to yield the permission mode that is applied to the file as it is created

In UNIX, each file has a set of attributes which control who can read, write or execute it. When a program creates a file, UNIX requires that the file permissions be set to an initial setting. The mask restricts permission settings. If the mask has a bit set to “1”, it means the corresponding initial file permission will be disabled. A bit set to “0” in the mask means that the corresponding permission will be determined by the program and the system. In other words, the mask acts as a last-stage filter that removes permissions as a file is created; each bit that is set to a “1” removes its corresponding permission. Permissions may be changed later by users and programs using chmod

reference: wikipedia

image: wikipedia

t-penned by netize R
No Comments

Sorry, the comment form is closed at this time.