topic Re: CHMOD in Operating System - HP-UX

CHMOD

kunjuttan — Tue, 19 Jul 2011 14:23:43 GMT

Hi,

I just created a new filesystem.I want to give full permission to all the files and directories creating inside this FS.How to achieve this.I tried with chmod -R 777 <FS>.But its not working.Please help me out...

Re: CHMOD

James R. Ferguson — Tue, 19 Jul 2011 14:31:29 GMT

Hi:

"But its not working" doesn't tell us a thing! What are you attempting to do (or see)? Where you root when you did the 'chmod'? What isn't the way you expect it to be?

...JRF...

Re: CHMOD

kunjuttan — Tue, 19 Jul 2011 14:34:11 GMT

thanks for the update..

i mean to say is chmod is wrking.....but if I create a new file inside this FS it is not having full permission.I want to create lot of files inside and all should be having full permission.

Re: CHMOD

Pete Randall — Tue, 19 Jul 2011 14:43:31 GMT

File creation is governed by the user's umask setting and 777 is not attainable with umask.

Re: CHMOD

James R. Ferguson — Tue, 19 Jul 2011 15:15:06 GMT

Hi (again):
@kunjuttan wrote:

thanks for the update..
i mean to say is chmod is wrking.....but if I create a new file inside this FS it is not having full permission.I want to create lot of files inside and all should be having full permission.

I assume that you want to be able to create files and have their permissions=777. This isn't going to be possible with the standard tools (like the shell).

When a file is created with 'open()' standard software supplies a 'mode' argument of octal 666 for files. This is built into the code and you can't change this unless you have access to the source. The effect of your 'umask' is to "subtract" from this value. Hence, a 'umask' of zero allows files thus created to have the "most open" permissions of 666.

To add execute permissons you are going to have to 'chmod' those files you want.

Regards!

...JRF...

Re: CHMOD

Dennis Handly — Tue, 19 Jul 2011 20:30:32 GMT

>chmod -R 777 <FS>

This is a very dangerous command. You do NOT want to add execute permission to non-executable files.

And do NOT use this on any existing system filesystems.

You should make several passes using find to select various file types and use the "+" symbolic permission operator:

find <FS> -type d -exec chmod a+x + # The last "+" is for find -exec performance

chmod -R a+rw <FS>