<?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: File mode in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191145#M9873</link>
    <description>This can be done by closing the directory for writing... Just do: 'chmod go-w .' while in the directory. This means they can't create files too, btw.&lt;BR /&gt;&lt;BR /&gt;Another way: set the 'sticky' bit on the directory: 'chmod o+s .' This has some other side effects (users can't remove files not owned by them.&lt;BR /&gt;&lt;BR /&gt;Test to see what's best for your situation.</description>
    <pubDate>Fri, 13 Feb 2004 03:18:09 GMT</pubDate>
    <dc:creator>Elmar P. Kolkman</dc:creator>
    <dc:date>2004-02-13T03:18:09Z</dc:date>
    <item>
      <title>File mode</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191144#M9872</link>
      <description>I have a file on the system , many users can access and update it , how can I fix the file mode ( eg. 666 ) , to prevent the user change the mode ? thx.</description>
      <pubDate>Fri, 13 Feb 2004 03:11:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191144#M9872</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-02-13T03:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: File mode</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191145#M9873</link>
      <description>This can be done by closing the directory for writing... Just do: 'chmod go-w .' while in the directory. This means they can't create files too, btw.&lt;BR /&gt;&lt;BR /&gt;Another way: set the 'sticky' bit on the directory: 'chmod o+s .' This has some other side effects (users can't remove files not owned by them.&lt;BR /&gt;&lt;BR /&gt;Test to see what's best for your situation.</description>
      <pubDate>Fri, 13 Feb 2004 03:18:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191145#M9873</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2004-02-13T03:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: File mode</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191146#M9874</link>
      <description>just make sure the file is not own by any users which you do not want to have ownership; maybe you want to own the file. AFAIK, you can only change mod if you own the file (besides all mighty powerfull root, offcourse).</description>
      <pubDate>Fri, 13 Feb 2004 09:48:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191146#M9874</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2004-02-13T09:48:05Z</dc:date>
    </item>
    <item>
      <title>Re: File mode</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191147#M9875</link>
      <description>Hello Peter,&lt;BR /&gt;&lt;BR /&gt;exactly which mode to set really depends on how this file is supposed to be used. Do all users on the system need rw to the fil? In that case 666 is the right protection. Do only users of one group need access? Chmod 660 would do that. &lt;BR /&gt;Ist is it a few users from different groups, add a new group, add the members to it, make the file owned by the group and again go 660. Users might need to do a chgrp to the right group in this case to gain access. If you need finegrained access have a look at ACLs.&lt;BR /&gt;&lt;BR /&gt;Greetings, Martin</description>
      <pubDate>Fri, 13 Feb 2004 14:48:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-mode/m-p/3191147#M9875</guid>
      <dc:creator>Martin P.J. Zinser</dc:creator>
      <dc:date>2004-02-13T14:48:16Z</dc:date>
    </item>
  </channel>
</rss>

