<?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 umask in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/umask/m-p/3576322#M229044</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;I have tried reading the man pages on umask but cant seem to get my head around it... can anyone explain to me what this is and how it is used and what the benefits of using umask are.&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Debbie</description>
    <pubDate>Tue, 05 Jul 2005 09:10:55 GMT</pubDate>
    <dc:creator>Debbie Downing_2</dc:creator>
    <dc:date>2005-07-05T09:10:55Z</dc:date>
    <item>
      <title>umask</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask/m-p/3576322#M229044</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I have tried reading the man pages on umask but cant seem to get my head around it... can anyone explain to me what this is and how it is used and what the benefits of using umask are.&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Debbie</description>
      <pubDate>Tue, 05 Jul 2005 09:10:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask/m-p/3576322#M229044</guid>
      <dc:creator>Debbie Downing_2</dc:creator>
      <dc:date>2005-07-05T09:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: umask</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask/m-p/3576323#M229045</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Please refer to following page of hp docs:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-90046/ch24s35.html" target="_blank"&gt;http://docs.hp.com/en/B2355-90046/ch24s35.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Mahesh</description>
      <pubDate>Tue, 05 Jul 2005 09:25:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask/m-p/3576323#M229045</guid>
      <dc:creator>Mahesh Kumar Malik</dc:creator>
      <dc:date>2005-07-05T09:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: umask</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/umask/m-p/3576324#M229046</link>
      <description>It's actually rather simple. First, it's easier if you think of file modes (permissions) in octal rather than symbolic form. 1 = execute; 2 = write; 4 = read. Next think of owner, group, other in terms of octal digits in that order as well. &lt;BR /&gt;&lt;BR /&gt;There are two components at play when a file is created. 1) Mode 2) Umask&lt;BR /&gt;&lt;BR /&gt;For example, the mode of a regular file under the shell is 666; umask then "subtracts" from this mode to yield the actual mode of the file. (It's not really subtraction but you can think of it this way.) Umask cannot put in what was not there so for example, you will never be able to create a file in the shell with the execute bit set because the execute bit is not set in the default mode. &lt;BR /&gt;&lt;BR /&gt;The idea behind umask is to make the system more secure. Again, with a regular file the default mode is 666. If umask were 000 then the actual mode of the file would be 666 but typically you would not want "other"s reading your file and greoup members shouldn't write to your file. A good umask for this, would be 026 or 027.</description>
      <pubDate>Tue, 05 Jul 2005 09:43:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/umask/m-p/3576324#M229046</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-07-05T09:43:11Z</dc:date>
    </item>
  </channel>
</rss>

