https://community.hpe.com/t5/operating-system-hp-ux/file-permission/m-p/5419965#M639869 <P>Thanx....<BR />:)</P> Fri, 16 Dec 2011 09:03:16 GMT Amdy_Sufiyan 2011-12-16T09:03:16Z https://community.hpe.com/t5/operating-system-hp-ux/file-permission/m-p/5419141#M639866 <P>what if&nbsp;user&nbsp;initially didn't give rwx permission to himself.</P> Thu, 15 Dec 2011 12:45:07 GMT https://community.hpe.com/t5/operating-system-hp-ux/file-permission/m-p/5419141#M639866 Amdy_Sufiyan 2011-12-15T12:45:07Z https://community.hpe.com/t5/operating-system-hp-ux/file-permission/m-p/5419165#M639867 <P>The simple answer is to use chmod. However, missing from your question is how the user was able to create a file without rwx permissions. When a user creates a file using vi or cp or touch or even file redirection, the setting for umask defines the initial mode for the file. In a new system where the (very bad) default for umask is 00, files will be created as -rw-rw-rw. NOTE: files should never be set to rwx UNLESS the file is a script (ksh, sh, perl, awk, etc). You do not want the x bit set on simple data files. If umask is 022, then permissions will default to -rw-r--r--</P><P>&nbsp;</P><P>If the user does not own the file, then the permissions (chmod) cannot be changed. Only the owner can modify the permissions.</P> Thu, 15 Dec 2011 13:05:56 GMT https://community.hpe.com/t5/operating-system-hp-ux/file-permission/m-p/5419165#M639867 Bill Hassell 2011-12-15T13:05:56Z https://community.hpe.com/t5/operating-system-hp-ux/file-permission/m-p/5419965#M639869 <P>Thanx....<BR />:)</P> Fri, 16 Dec 2011 09:03:16 GMT https://community.hpe.com/t5/operating-system-hp-ux/file-permission/m-p/5419965#M639869 Amdy_Sufiyan 2011-12-16T09:03:16Z