This is the mail archive of the
mailing list for the Cygwin project.
Re: umask (was:Re: gcc, Write and Modify permissions (ntsec))
- From: Roman Belenov <rbelenov at yandex dot ru>
- To: cygwin at cygwin dot com
- Date: Thu, 05 Dec 2002 10:36:42 +0300
- Subject: Re: umask (was:Re: gcc, Write and Modify permissions (ntsec))
- References: <firstname.lastname@example.org><20021129134919.C1398@cygbert.vinschen.de> <email@example.com><20021129134919.C1398@cygbert.vinschen.de><firstname.lastname@example.org>
I usually use FAR manager (non-cygwin Norton Commander clone) (*) for
command-line work and run cygwin programs (like grep, gcc or make)
from it; modifying all programs or writings wrapper scripts for them
is not an option.
May be it makes sense to add umask option to CYGWIN environment
variable ? Probably there are other users with usage pattern similar
(*) I know about Midnight Commander and use it on Linux, but FAR is
more usable on Windows.
Randall R Schulz <email@example.com> writes:
> At 08:00 2002-12-04, Randall R Schulz wrote:
>> Have them call umask(2). If that's not an option, invoke them via a
>> Cygwin shell script that changes the umask first--it's my child
>> processes just as environment variables are.
> I don't know what kind of editing snafu that was, but I meant:
> "... It's inherited by child processes just as ..."
>>Mountain View, CA USA
>>At 23:44 2002-12-03, Roman Belenov wrote:
>>>Corinna Vinschen <firstname.lastname@example.org> writes:
>>> > umask
>>>How can I change umask of processes launched from Windows executables?
With regards, Roman.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html