On Wed, 29 Sep 2004, Bob Showalter wrote: > Chris Devers wrote: > > > Maybe the program is a code generator that produces other > > files which should be executable (I can't remember anyone doing this, > > but there's no reason why it couldn't be reasonably be done). > > Fine, use creation bits of 0777. > > Neither of these require fooling with umask.
Did I say umask was required? If so, that wasn't what I meant. I'm not getting into the mechanism of how permissions get set; I'm saying that there are clear, justifiable cases where a program can have a legitmate need to set permissions in any way the programmer sees fit. The user of such a program may choose to override these settings, but that may or may not invalidate the reasons for originally setting them. > My gripe is with a program that decides a file _needs_ to be created > as 666, for example. Everything has a place. Sometimes it can make sense. -- Chris Devers -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
