On Wed, Nov 29, 2000 at 11:29:52AM -0800, Todd A. Jacobs wrote:
[...]
>
> chmod g+rw /work/*
>
> Using a recursive chmod will unfortunately unset the execute bit on
> directories, or perhaps set the execute bit on files which should be
> executable.
That is only true if you use octal modes. A chmod command like the one above
(i.e. "g+rw") doesn't touch the "x" flags at all.
As a matter of fact, I'm using
chmod -R g+rw *
on one of my directory trees on a regular basis (for the same reasons as
the original poster) with no ill effects.
If you use octal modes instead of the string ones, there might be trouble
- "chmod 644 *" *will* unset the "x" flag, whereas "chmod g+rw *" won't.
That's the beauty of giving the permissions as string rather than as octal.
Cheerio,
Thomas
P.S.: Another nice thing (though unrelated to the present problem), btw, is
"chmod -R g+X *" (that's a capital X)
--
"Look, Ma, no obsolete quotes and plain text only!"
Thomas Ribbrock | http://www.bigfoot.com/~kaytan | ICQ#: 15839919
"You have to live on the edge of reality - to make your dreams come true!"
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
