in this unix book that i have, it says:
the statement:
filedes = open(pathname, O_CREAT, mode);
is actually
filedes = open(pathname, O_CREAT, (~mask)&mode); /* ~ is the negation symbol */
like it's doing some type of masking.
for example,
fd =... (1 Reply)
I changed the umask in /etc/security/user to 027.
I changed the umask in /etc/profile to 027.
My current shell is ksh.
My .profile doesn't make any changes to umask or call other scripts that change umask.
Running AIX 5.3
I still get a umask of 022 instead of the expected 027. I have no... (1 Reply)
hai guys ,
i am having problem in getting the knowledge about umask.
actually when i am putting command as umask some value is coming like 0022 by defalut.
we can change its value also.
but the main thing is thye file permisiion actually depends upon umask.how is it depends upon umask i want to... (6 Replies)
Hi,
I have a doubt on the umask values.
Why is the UMASK value is different from file and directory?
Suppose if the umask value is 0022. The file permissions for a newly created file is 644 and the file permissions for a newly created directory is 755.
My doubt is why can't it be the... (1 Reply)
Due to urgent requirement to resolve some permission issues , I wish
to set solaris 8 server so that any file written is on 777 .
I guess need to set umask , how to set it ?? (7 Replies)
Hi,
Please, let me know how the umask is working? As per my understanding is aprt from subtracting from 666/777, logical gate operation is performing.
Ex: If I set uname 011, it gave the permission like 666 for file. Request you to explain which gate's operation performed.
$uname 011... (4 Replies)
Hi,
I want to set umask value only for vi editor.
If I create new file using vi editor, then automatic permission should be 777.
I want to set umask 000.
Please help me.
Thanks in advance (2 Replies)
Hi guys,
I want all new files and directories created, or copy file give this permisson "rwxrwx---", with chmod i do this with octal value "770". If i execute "umask 770" the permissons is not the same with new or copy file. How can i configure this command? I do not understand the "man... (1 Reply)
Perl::Critic::Policy::Variables::ProhibitAugmentedAssignUserIContributPerl::Critic::Policy::Variables::ProhibitAugmentedAssignmentInDeclaration(3)NAME
Perl::Critic::Policy::Variables::ProhibitAugmentedAssignmentInDeclaration - Do not write " my $foo .= 'bar'; ".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Variable declarations that also do initialization with '=' are common. Perl also allows you to use operators like '.=', '+=', etc., but it
it is more clear to not do so.
my $foo .= 'bar'; # same as my $foo = 'bar';
our $foo *= 2; # same as our $foo = 0;
my ( $foo, $bar ) += ( 1, 2 ); # same as my ( $foo, $bar ) = ( undef, 2 );
local $Carp::CarpLevel += 1; # same as local $Carp::CarpLevel = 1;
state $foo += 2; # adds 2 every time it's encountered
Such constructs are usually the result of botched cut-and-paste, and often are bugs. Some produce warnings.
CONFIGURATION
This Policy is not configurable except for the standard options.
AUTHOR
Mike O'Regan
COPYRIGHT
Copyright (c) 2011 Mike O'Regan. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.320Perl::Critic::Policy::Variables::ProhibitAugmentedAssignmentInDeclaration(3)