[SOLVED] Command line: chown command recursively on invisible directories?

JZL240I-U · 10-25-2010, 05:03 AM

I tried

Code:

chown -R owner:group *

which does not work on the invisible directories (why?). When I used ".*" as wildcard it changed all (visible) files including the parent directory (the one I was currently working in which is the "dot")

.

I can change the invisible directories owner and group using dophin but how is it done from the command line?

neonsignal · 10-25-2010, 05:44 AM

You can change the glob expansion to include hidden files by setting the dotglob shell option:

Code:

shopt -s dotglob; chown -R owner:group *; shopt -u dotglob

kilgoretrout · 10-25-2010, 05:47 AM

I never noticed that but it may be something in how the wild card designation "*" works in conjunction with the "R" flag. Normally, I would run the command using the full path to the directory whose files I wanted to recursively change the ownership of, eg:

$ chown -R owner:group <path to target directory>

Try it that way and see if it works on the hidden directories/files contained in your target directory.

GrapefruiTgirl · 10-25-2010, 05:56 AM

In the interest of "more ways to do things", you can also escape the "." to chown any/all files/directories:

Code:

root@reactor: ls -laR
.:
total 76
drwxr-xr-x 4 root root  4096 Oct 25 07:38 .
drwxr-xr-x 9 root root  4096 Oct 22 18:11 ..
-rw-r--r-- 1 root root    23 Oct 23 19:16 .dashfile.sh
drwxr-xr-x 2 root root  4096 Oct 25 07:43 .hidden_dir
drwxr-xr-x 2 root root  4096 Oct 24 20:02 Radio-test
-rw-r--r-- 1 root root    24 Oct 22 18:12 bashfile-space.sh
-rw-r--r-- 1 root root    23 Oct 22 18:12 bashfile.sh
-rw-r--r-- 1 root root    24 Oct 22 18:12 dashfile-space.sh
-rw-r--r-- 1 root root    23 Oct 22 18:12 dashfile.sh
-rwxr-xr-x 1 root root    78 Oct 23 22:15 getopts_tester.sh
-rw-r--r-- 1 root root 15933 Oct 22 21:00 script_locator.output
-rwxr-xr-x 1 root root  1381 Oct 23 12:15 script_locator.sh
-rw-r--r-- 1 root root    22 Oct 22 18:12 shfile-space.sh
-rw-r--r-- 1 root root    21 Oct 22 18:13 shfile.sh
-rw-r--r-- 1 root root   485 Oct 22 20:15 somefile
-rwxr-xr-x 1 root root    24 Oct 23 13:26 testing

./.hidden_dir:
total 8
drwxr-xr-x 2 root root 4096 Oct 25 07:43 .
drwxr-xr-x 4 root root 4096 Oct 25 07:38 ..
-rw-r--r-- 1 root root    0 Oct 25 07:43 .hidden_file



root@reactor: chown -R sasha:users \.*
root@reactor: ls -laR
.:
total 76
drwxr-xr-x 4 sasha users  4096 Oct 25 07:38 .
drwxr-xr-x 9 sasha users  4096 Oct 22 18:11 ..
-rw-r--r-- 1 sasha users    23 Oct 23 19:16 .dashfile.sh
drwxr-xr-x 2 sasha users  4096 Oct 25 07:43 .hidden_dir
drwxr-xr-x 2 sasha users  4096 Oct 24 20:02 Radio-test
-rw-r--r-- 1 sasha users    24 Oct 22 18:12 bashfile-space.sh
-rw-r--r-- 1 sasha users    23 Oct 22 18:12 bashfile.sh
-rw-r--r-- 1 sasha users    24 Oct 22 18:12 dashfile-space.sh
-rw-r--r-- 1 sasha users    23 Oct 22 18:12 dashfile.sh
-rwxr-xr-x 1 sasha users    78 Oct 23 22:15 getopts_tester.sh
-rw-r--r-- 1 sasha users 15933 Oct 22 21:00 script_locator.output
-rwxr-xr-x 1 sasha users  1381 Oct 23 12:15 script_locator.sh
-rw-r--r-- 1 sasha users    22 Oct 22 18:12 shfile-space.sh
-rw-r--r-- 1 sasha users    21 Oct 22 18:13 shfile.sh
-rw-r--r-- 1 sasha users   485 Oct 22 20:15 somefile
-rwxr-xr-x 1 sasha users    24 Oct 23 13:26 testing

./.hidden_dir:
total 8
drwxr-xr-x 2 sasha users 4096 Oct 25 07:43 .
drwxr-xr-x 4 sasha users 4096 Oct 25 07:38 ..
-rw-r--r-- 1 sasha users    0 Oct 25 07:43 .hidden_file

JZL240I-U · 10-25-2010, 06:27 AM

@neonsignal: Thanks for an extremely concise, but to the point, correct and complete solution (man pages helped to understand the background, as usual

).

@kilgoretrout: I'll try it tomorrow, I'm not at home now.

@GrapefruiTgirl: True to the spirit, I see. And with the escaping scheme the least typing work. Kudos.

Thank you all for your input.

JZL240I-U · 10-28-2010, 05:01 AM

@kilgoretrout: Works with path exactly as you said it would. Thanks again.

neonsignal · 10-28-2010, 06:04 AM

Quote:

Originally Posted by JZL240I-U

Works with path exactly as you said it would.

Keep in mind that using chown with the full path is no different to using it on '.', and will also change the ownership on the directory itself (which may be what you want).

ie, this:

Code:

chown -R owner:group /home/user/test/

will do the same as this:

Code:

cd /home/user/test
chown -R owner:group .

JZL240I-U · 10-28-2010, 02:22 PM

Quote:

Originally Posted by neonsignal

Keep in mind that using chown with the full path is no different to using it on '.', and will also change the ownership on the directory itself (which may be what you want).

It is what I wanted. But I have a problem to understand the exact difference between

Code:

chown -R owner:group * 

and 

hown -R owner:group .

The first I tried with the unwanted results. But what is the difference for "bash"?

neonsignal · 10-28-2010, 05:14 PM

Quote:

Originally Posted by JZL240I-U

understand the exact difference between

Code:

chown -R owner:group * 
and 
chown -R owner:group .

In the second of these, bash hands the '.' to chown. The chown is then applied to that file (which is the current working directory), and recursively to any files below it in the file hierarchy. Hidden files are not treated any differently by chown.

In the first of these, bash expands the '*' glob before handing the list to chown. The default is to expand it to a list of all the files in the current working directory, not including hidden files. So chown is being applied to this list, and recursively to files below that, but not to the current working directory. Since the names of hidden files were not even handed to chown, there is no reason for it to change them.

Incidentally, using '.*' has even worse side effects. Because not only does it include the current working directory, but it also includes the parent directory '..'. So the chown will not only be applied to the parent, but recursively to all the files/directories in the parent directory (ie, 'siblings' of the current working directory). Escaping the '.' does not change the behaviour, because the '.' is not a special character.

You can use echo to see the actual commands that would be run after the glob expansion, which may make it clearer:

Code:

echo chown -R owner:group * 
echo chown -R owner:group .
echo chown -R owner:group .*

JZL240I-U · 10-29-2010, 04:34 AM

Ahhh, now I get it. Again an exceptionally lucid answer. The trick with "echo" is super as well, I'll remember that one. Kudos and thanks, neonsignal

.

P.S.: Anybody of all these gurus here ready for a take on this one:

http://www.linuxquestions.org/questi...ns-why-840925/