<?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: chown -r me:group .* misunderstanding effects in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937776#M46340</link>
    <description>I always change the . files manually because of what you just described. I had the same movie in my eyes at that time as well.&lt;BR /&gt;&lt;BR /&gt;There is a way using the ? symbol but have not researched enough. the manual method may take longer but I do feel safer.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 01 Nov 2005 13:55:57 GMT</pubDate>
    <dc:creator>Rick Garland</dc:creator>
    <dc:date>2005-11-01T13:55:57Z</dc:date>
    <item>
      <title>chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937775#M46339</link>
      <description>The good news is that this is a development system.  At login I discovered that I landed in / rather than $HOME - /usr/users/mydir.  I su'd to root, and discovered that I did not own my $HOME directory and files in it and below it.&lt;BR /&gt;&lt;BR /&gt;In order to correct this as root I executed&lt;BR /&gt;&lt;BR /&gt;$ cd /usr/users&lt;BR /&gt;$ chown me:mygroup mydir&lt;BR /&gt;$ cd /usr/users/mydir&lt;BR /&gt;$ chown -R me:mygroup *&lt;BR /&gt;&lt;BR /&gt;The result was all files in and below $HOME received me:mygroup ownership.  Excellent!&lt;BR /&gt;&lt;BR /&gt;This left the ownership of the hidden files/dirs in $HOME unchanged.  In $HOME I then executed&lt;BR /&gt;chown -R me:mygroup .*&lt;BR /&gt;&lt;BR /&gt;Lo and behold, the command traveled up a level to /usr/users and then down through ALL /usr/users, making me:mygroup the owner.  My career passed in front of my eyes.&lt;BR /&gt;&lt;BR /&gt;Please help me understand the chown syntax or file specification wildcard mis-understanding/ignorance I am operating under.&lt;BR /&gt;&lt;BR /&gt;I have searched ITRC with no relevant references found.  If there is a relevant article please provide a pointer.  Thanks for your help.&lt;BR /&gt;&lt;BR /&gt;Joe S.</description>
      <pubDate>Tue, 01 Nov 2005 12:57:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937775#M46339</guid>
      <dc:creator>Joseph P. Smith</dc:creator>
      <dc:date>2005-11-01T12:57:11Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937776#M46340</link>
      <description>I always change the . files manually because of what you just described. I had the same movie in my eyes at that time as well.&lt;BR /&gt;&lt;BR /&gt;There is a way using the ? symbol but have not researched enough. the manual method may take longer but I do feel safer.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Nov 2005 13:55:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937776#M46340</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-11-01T13:55:57Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937777#M46341</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;this .* is not chown syntax but shell  special pattern.&lt;BR /&gt;&lt;BR /&gt;look at results of command:&lt;BR /&gt;1. echo .* &lt;BR /&gt;. ..&lt;BR /&gt;this means your command was interpreted by shell as:&lt;BR /&gt;chown -R me:mygroup . ..&lt;BR /&gt;&lt;BR /&gt;when you want to change permisions or owner to .* files and directores you should use syntax:&lt;BR /&gt;&lt;BR /&gt;chown -R me:mygroup .??*&lt;BR /&gt;where ? - Matches any single character.&lt;BR /&gt;Don't use single ? because:&lt;BR /&gt;echo .?  -&amp;gt; means ..&lt;BR /&gt;&lt;BR /&gt;But in your example the best/easiest solution to change owner of all files and dirs was:&lt;BR /&gt;cd /usr/users&lt;BR /&gt;chown -R me:mygroup mydir&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Nov 2005 14:02:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937777#M46341</guid>
      <dc:creator>Slawomir Gora</dc:creator>
      <dc:date>2005-11-01T14:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937778#M46342</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;if you use ".*" you also select the directory ".." which is the parent directory. The option -r will now change all right in all selected directory, even in the parent directory and all subfolders of the parent directory.&lt;BR /&gt;&lt;BR /&gt;To avoid this i always use ".??*" and handle all dot-files matching ".?" manually.&lt;BR /&gt;&lt;BR /&gt;HeL</description>
      <pubDate>Tue, 01 Nov 2005 14:05:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937778#M46342</guid>
      <dc:creator>Heiner E. Lennackers</dc:creator>
      <dc:date>2005-11-01T14:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937779#M46343</link>
      <description>Thank you all.  Slawomir Gora gets the rabitt!  Anyone know how that gets assigned?&lt;BR /&gt;&lt;BR /&gt;I had better know how the shell special characters are interpreted.  The suggestions of .??* and correct directory spec are very useful.  Thnx again.&lt;BR /&gt;&lt;BR /&gt;Joe S.</description>
      <pubDate>Tue, 01 Nov 2005 14:22:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937779#M46343</guid>
      <dc:creator>Joseph P. Smith</dc:creator>
      <dc:date>2005-11-01T14:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937780#M46344</link>
      <description>The best solution has already been given (chown  -R the directory from the parent level).&lt;BR /&gt;&lt;BR /&gt;Other pattern matching that will work:&lt;BR /&gt;&lt;BR /&gt;chown -R me:mygroup .[A-z]*&lt;BR /&gt;&lt;BR /&gt;will catch any file or directory beginning with . followed by any letter.&lt;BR /&gt;&lt;BR /&gt;You could extend this to include numbers and other characters.&lt;BR /&gt;&lt;BR /&gt;Or:&lt;BR /&gt;&lt;BR /&gt;chown -R me:mygroup .[!.]*&lt;BR /&gt;&lt;BR /&gt;which will match any file or directory beginning with a . and followed by any character, but *NOT* a second . (i.e. "dot-not-dot-but-anything-else")&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Andy Bruce&lt;BR /&gt;</description>
      <pubDate>Wed, 02 Nov 2005 04:43:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937780#M46344</guid>
      <dc:creator>Andrew Bruce</dc:creator>
      <dc:date>2005-11-02T04:43:41Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937781#M46345</link>
      <description>I forgot to add:&lt;BR /&gt;&lt;BR /&gt;for more information, have a look in the man page for the shell you are using (e.g. man bash) and look for the explanation of pattern matching.&lt;BR /&gt;&lt;BR /&gt;Indeed, if you do a "man bash" and search for:&lt;BR /&gt;&lt;BR /&gt;Pattern Matching&lt;BR /&gt;&lt;BR /&gt;The second occurrence is the section you want to read up on!&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Andy Bruce&lt;BR /&gt;&lt;BR /&gt;ps if you're dishing out points, don't give me double as I meant to put this bit in with my first respone! ;-)</description>
      <pubDate>Wed, 02 Nov 2005 04:47:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937781#M46345</guid>
      <dc:creator>Andrew Bruce</dc:creator>
      <dc:date>2005-11-02T04:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937782#M46346</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;you could have done it with&lt;BR /&gt;chown -R me:mygroup /usr/users/mydir&lt;BR /&gt;This would have included all . files as well.&lt;BR /&gt;chown -R .* is very dangerous as said.&lt;BR /&gt;I wrecked a production system twice. :-(&lt;BR /&gt;I was new into Unix and I tried to set the owner of the .* files.&lt;BR /&gt;Luckily the sysadmin did have a few open windows at all times so he could repair it.&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Nov 2005 10:46:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937782#M46346</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-11-03T10:46:33Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937783#M46347</link>
      <description>Closing thread &amp;amp; thanks to all.  Going to the firinq squad!  ;-)  [not really]&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Nov 2005 11:23:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937783#M46347</guid>
      <dc:creator>Joseph P. Smith</dc:creator>
      <dc:date>2005-11-03T11:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: chown -r me:group .* misunderstanding effects</title>
      <link>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937784#M46348</link>
      <description>As stated above.&lt;BR /&gt;Joe S.</description>
      <pubDate>Thu, 03 Nov 2005 11:24:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/chown-r-me-group-misunderstanding-effects/m-p/4937784#M46348</guid>
      <dc:creator>Joseph P. Smith</dc:creator>
      <dc:date>2005-11-03T11:24:16Z</dc:date>
    </item>
  </channel>
</rss>

