force create permissions

chesterman · 11-21-2009, 05:55 AM

is there a way to enforce that a file created on a directory will inherit the owner/groupship of the his parent folder?

tronayne · 11-21-2009, 06:50 AM

If you mean with, say, the cp utility then yes you can use the --preserve option; e.g.,

Code:

cp --preserve=all file directory

See the man page.

Hope this helps some.

chesterman · 11-21-2009, 07:45 AM

there is a proccess running as root (i now this is not the good thing to do, but is the way is running now, and it can't be changed in some months) that create tons of files in a folder. i have to sync this files with a twin folder on other machine, but there is no root access by ssh between the 2 machines.

also, in the twin machine, the process is running with limited user (the right thing), so while I can not change this process to run as root on original machine, I want the files it creates have the folder permissions, and not his.

tronayne · 11-21-2009, 09:32 AM

If you can read the files from the other machine (with, say, scp) and have your umask set properly, the files should copy with "your" owner and group; that is, whatever user account is doing the copying will be the owner and group of the copied files and the files will have permission defined by your system umask setting (which probably ought to be 0022 which creates files 0644 and directories 0755).

Hope this helps some.

lwasserm · 11-21-2009, 10:07 AM

If the the directory has the setgid bit set then files created in it will have group ownership of the directory. You can set it like this:

Code:

$ mkdir directory
$ ls -ld directory
drwx------ 2 lwasserm lwasserm 4096 2009-11-21 11:04 directory
$ chmod g+s directory
$ ls -ld directory
drwx--S--- 2 lwasserm lwasserm 4096 2009-11-21 11:04 directory

When you see the 'S' in the group permissions field it is set correctly for this behaviour.

Just a note, I believe files "moved" into the directory, rather than created in it, will retain their original group.

chesterman · 11-23-2009, 12:44 PM

hey, it worked =D
worked just with the files created inside the folder, and just for the groupship. files moved into the folder did not get changed.

tks guys =D

chesterman · 11-23-2009, 01:26 PM

what's the difference between

Code:

drwx--S--- 2 lwasserm lwasserm 4096 2009-11-21 11:04 directory

and

Code:

drwx--s--- 2 lwasserm lwasserm 4096 2009-11-21 11:04 directory

?

lwasserm · 11-23-2009, 03:20 PM

Quote:

Originally Posted by chesterman

what's the difference between

Code:

drwx--S--- 2 lwasserm lwasserm 4096 2009-11-21 11:04 directory

and

Code:

drwx--s--- 2 lwasserm lwasserm 4096 2009-11-21 11:04 directory

?

A lower case s indicates the file is also executable for the group. You would probably need that on subdirectories too.