<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: umask command ... in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723596#M253363</link>
    <description>If you set a umask of 000 then files will be created with permissions of 666 (-rw-rw-rw-) and directories with permissions of 777 (drwxrwxrwx).&lt;BR /&gt;&lt;BR /&gt;You CAN NOT force a file to be created with 777 permissions.  If you need the execute permission on a file it must be set manually with the chmod command.</description>
    <pubDate>Fri, 03 Feb 2006 00:01:37 GMT</pubDate>
    <dc:creator>Patrick Wallek</dc:creator>
    <dc:date>2006-02-03T00:01:37Z</dc:date>
    <item>
      <title>umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723593#M253360</link>
      <description>Hi, can you tell me how can i use umask command? i mean, i need that every time is generated a file in operating system with touch command or cat command, i need that appear with all the permissions ...&lt;BR /&gt;&lt;BR /&gt;how can i do it?&lt;BR /&gt;&lt;BR /&gt;Thanks, Manuales.</description>
      <pubDate>Thu, 02 Feb 2006 22:43:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723593#M253360</guid>
      <dc:creator>Manuales</dc:creator>
      <dc:date>2006-02-02T22:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723594#M253361</link>
      <description>umask controls the file/dirs perms of a newly created file. With umask, you can not have a file with execute perm. That is by design itself. You can have all other perms but not execute perms.&lt;BR /&gt;e.g. umask of 0000 will create a file with rw perms for all.&lt;BR /&gt;&lt;BR /&gt;Basically, the umask value is substracted from 666 for effective perms for files and umask value is subtracted from 777 for effective perms on a dir.&lt;BR /&gt;&lt;BR /&gt;man umask for details.</description>
      <pubDate>Thu, 02 Feb 2006 22:59:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723594#M253361</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2006-02-02T22:59:32Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723595#M253362</link>
      <description>if i want that all files created have all permissions, how do i must writte the umansk command parameters?&lt;BR /&gt;&lt;BR /&gt;umask 0000?&lt;BR /&gt;umask 7777?&lt;BR /&gt;umask 6666?&lt;BR /&gt;umask 5555?&lt;BR /&gt;&lt;BR /&gt;which one?&lt;BR /&gt;&lt;BR /&gt;Thanks, Manuales.</description>
      <pubDate>Thu, 02 Feb 2006 23:49:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723595#M253362</guid>
      <dc:creator>Manuales</dc:creator>
      <dc:date>2006-02-02T23:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723596#M253363</link>
      <description>If you set a umask of 000 then files will be created with permissions of 666 (-rw-rw-rw-) and directories with permissions of 777 (drwxrwxrwx).&lt;BR /&gt;&lt;BR /&gt;You CAN NOT force a file to be created with 777 permissions.  If you need the execute permission on a file it must be set manually with the chmod command.</description>
      <pubDate>Fri, 03 Feb 2006 00:01:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723596#M253363</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2006-02-03T00:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723597#M253364</link>
      <description>I need to add the having files and directories with wide-open permissions is a VERY VERY BAD practice.  This allows anyone and everyone logged onto the system to read/modify/remove/whatever the files.  Very bad idea for security on a system.</description>
      <pubDate>Fri, 03 Feb 2006 00:04:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723597#M253364</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2006-02-03T00:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723598#M253365</link>
      <description>&lt;BR /&gt;Hi Mauales,&lt;BR /&gt;&lt;BR /&gt;By default you CANNOT CREATE a file with executable permission, by setting the umask value you can make the default permission to "rw" for everyone.&lt;BR /&gt;&lt;BR /&gt;But you can make it executable only by executing &lt;BR /&gt;&lt;BR /&gt;#chmod &lt;BR /&gt;&lt;BR /&gt;manually.&lt;BR /&gt;&lt;BR /&gt;With Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.</description>
      <pubDate>Fri, 03 Feb 2006 01:07:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723598#M253365</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2006-02-03T01:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723599#M253366</link>
      <description>Default mask of umask 000 will create files with permission of 666 and directory as 777. &lt;BR /&gt;&lt;BR /&gt;We have to have executable permission in a directory for browsing or searching. Meantime, file must not have the executable permission. It has to be changed by the user or group or world wide permission for execution. &lt;BR /&gt;&lt;BR /&gt;Use the method of having default umask setting and use chmod command to change mode value.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu</description>
      <pubDate>Fri, 03 Feb 2006 01:15:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723599#M253366</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-02-03T01:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723600#M253367</link>
      <description>hi Man,&lt;BR /&gt;&lt;BR /&gt;umask can be added in users .profile or /etc/profile.&lt;BR /&gt;&lt;BR /&gt;Def will be 022 on the profile.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Chan</description>
      <pubDate>Sat, 04 Feb 2006 12:29:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723600#M253367</guid>
      <dc:creator>Chan 007</dc:creator>
      <dc:date>2006-02-04T12:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: umask command ...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723601#M253368</link>
      <description>Hi Manuales:&lt;BR /&gt;&lt;BR /&gt;As RAC noted, the manpages for 'umask' offer a reasonable explanation.&lt;BR /&gt;&lt;BR /&gt;A reasonable 'umask' to set in your login profiles is 022, with 027 being a "strong" setting.&lt;BR /&gt;&lt;BR /&gt;Remember that a *directory's* permissions control whether or not a file can be removed.  If you have write permissions to a directory, you can remove a file that you own from it.&lt;BR /&gt;&lt;BR /&gt;A directory like '/tmp', however, is often granted read-write-execute permissions for everyone.  This is quite reasonable.   However, the side-effect of this is that *anyone* can remove *any* file from this directory regardless of who owns it.&lt;BR /&gt;&lt;BR /&gt;To limit non-root users to being able to remove only files they own, set the 'sticky' bit on the directory:&lt;BR /&gt;&lt;BR /&gt;# chmod 1777 /tmp&lt;BR /&gt;&lt;BR /&gt;See also my *last* comments in a similar thread where you asked a related question but closed the thread after asking but before reading:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=998150" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=998150&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 04 Feb 2006 13:22:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask-command/m-p/3723601#M253368</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-02-04T13:22:13Z</dc:date>
    </item>
  </channel>
</rss>

