Re: Xcode 2.4.1 locking build directories after build
Re: Xcode 2.4.1 locking build directories after build
- Subject: Re: Xcode 2.4.1 locking build directories after build
- From: Mike <email@hidden>
- Date: Fri, 31 Aug 2007 15:31:28 -0700
That indeed was the problem and adding the umask line you suggested did
the trick.
Thanks,
Mike
Greg Guerin wrote:
Mike wrote:
I am running my 1st shell script using sudo which then fires off 3 or 4
other shell scripts to build my product.
Unix Files 101: the default permissions for creating files and dirs are
affected by the umask value, which is inherited by processes. The default
value for umask is 022 (octal), which clears the w bits for group and
other. If you don't change umask, then the default 022 will be applied.
To prevent the masking of group-write, i.e. to allow group-write by
default, the umask value should be 002 (octal). The shell command for this
is:
umask 002
You should issue this command in your sudo'ed shell script. It will then
be inherited by its child processes.
The build dirs don't have the red lock icon on them, just their x bits
cleared for group and others (but not for owner) in the filesystem.
Now I'm confused. You wrote this before:
...it is clearing the "w" bit for group and others...
So is it the w bit(s) or the x bit(s) that are cleared?
Please post an ls -lR for a section of the build-tree that's presenting the
problem.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden