10 More Discussions You Might Find Interesting
1. Solaris
Hi,
Any ideas to set multiple ownership permission on a file/directory on Solaris? I need a folder to have multiple ownership on the 2 nodes servers. The 2 nodes servers require to mount a SMBFS with different user ID. Please assist. Thanks. (6 Replies)
Discussion started by: freshmeat
6 Replies
2. UNIX for Dummies Questions & Answers
When am saving a file using my username in Linux environment, the file permission granted is rw-r--r--
I have to manually change the permissions using chmod command.
How do i write it to the disk as rw-rw-r while saving my file. (6 Replies)
Discussion started by: Avishek_rc1
6 Replies
3. UNIX for Dummies Questions & Answers
Hey Guys,
First post here. I just started learning UNIX a few weeks ago.
My issue: I use FreeNAS which is based off of UNIX in my network environment which hosts files that my team needs to access. Each user has their own login but we are all part of a group called "ITLIC".
I have a share... (15 Replies)
Discussion started by: uglycustoomer
15 Replies
4. Solaris
hi every one
"plz any one can give solution to my problem" my problem is my filesystem is full in os level i have to decrease it to 60% how can i? plz help me
Thank you for your response (6 Replies)
Discussion started by: sivajerripothul
6 Replies
5. Shell Programming and Scripting
Here is the sample code I'm trying to execute. I see that the permission on the file is set to 755 always I want to change it to 777. Please help me with this.
code :
#!/usr/bin/perl
use File::Path qw(make_path remove_tree);
my $path = "2010/sam";
make_path($path,{mode=>0777});
... (1 Reply)
Discussion started by: hansini
1 Replies
6. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
7. Shell Programming and Scripting
Hi, all!
Is it possible to use umask and to set the file permission level as 775?
I know I can add chmod into my scripts but I just want to explore the umask option.
Thanks! (1 Reply)
Discussion started by: visio2000
1 Replies
8. UNIX for Dummies Questions & Answers
Hi there,
I want to change from this permission -r-xr-xr-x to -r-xr-xr-- for a set of files under unix.
Can someone help me to go-about doing this in one shot.
Cheers,
RN (2 Replies)
Discussion started by: karthickrn
2 Replies
9. AIX
Trying to setup user to have the ability to delete any files (regardless of owner) in /tmp.
I've tried almost everything... the permission on the folder is drwxrwxrwt 10 bin bin, and at one point I give all the possible permission (short of root) I can give to the user, and he still can't delete... (2 Replies)
Discussion started by: cchiang12
2 Replies
10. UNIX for Dummies Questions & Answers
Under this directory:
/var/spool/cron/crontabs/
I have the following users:
adm lp oracle root sys uucp
I believe who are able to start a cron job.
I am trying to create a cronjob under user banjob so that it can delete files older than 30 days.
How can I add user banjob... (4 Replies)
Discussion started by: simt
4 Replies
CHMOD(1) FSF CHMOD(1)
NAME
chmod - change file access permissions
SYNOPSIS
chmod [OPTION]... MODE[,MODE]... FILE...
chmod [OPTION]... OCTAL-MODE FILE...
chmod [OPTION]... --reference=RFILE FILE...
DESCRIPTION
This manual page documents the GNU version of chmod. chmod changes the permissions of each given file according to mode, which can be
either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new permissions.
The format of a symbolic mode is `[ugoa...][[+-=][rwxXstugo...]...][,...]'. Multiple symbolic operations can be given, separated by com-
mas.
A combination of the letters `ugoa' controls which users' access to the file will be changed: the user who owns it (u), other users in the
file's group (g), other users not in the file's group (o), or all users (a). If none of these are given, the effect is as if `a' were
given, but bits that are set in the umask are not affected.
The operator `+' causes the permissions selected to be added to the existing permissions of each file; `-' causes them to be removed; and
`=' causes them to be the only permissions that the file has.
The letters `rwxXstugo' select the new permissions for the affected users: read (r), write (w), execute (or access for directories) (x),
execute only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s), sticky
(t), the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group
(g), and the permissions granted to users that are in neither of the two preceding categories (o).
A numeric mode is from one to four octal digits (0-7), derived by adding up the bits with values 4, 2, and 1. Any omitted digits are
assumed to be leading zeros. The first digit selects the set user ID (4) and set group ID (2) and sticky (1) attributes. The second digit
selects permissions for the user who owns the file: read (4), write (2), and execute (1); the third selects permissions for other users in
the file's group, with the same values; and the fourth for other users not in the file's group, with the same values.
chmod never changes the permissions of symbolic links; the chmod system call cannot change their permissions. This is not a problem since
the permissions of symbolic links are never used. However, for each symbolic link listed on the command line, chmod changes the permis-
sions of the pointed-to file. In contrast, chmod ignores symbolic links encountered during recursive directory traversals.
STICKY FILES
On older Unix systems, the sticky bit caused executable files to be hoarded in swap space. This feature is not useful on modern VM sys-
tems, and the Linux kernel ignores the sticky bit on files. Other kernels may use the sticky bit on files for system-defined purposes. On
some systems, only the superuser can set the sticky bit on files.
STICKY DIRECTORIES
When the sticky bit is set on a directory, files in that directory may be unlinked or renamed only by root or their owner. Without the
sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on directories, such as
/tmp, that are world-writable.
OPTIONS
Change the mode of each FILE to MODE.
-c, --changes
like verbose but report only when a change is made
-f, --silent, --quiet
suppress most error messages
-v, --verbose
output a diagnostic for every file processed
--reference=RFILE
use RFILE's mode instead of MODE values
-R, --recursive
change files and directories recursively
--help display this help and exit
--version
output version information and exit
Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxXstugo.
AUTHOR
Written by David MacKenzie.
REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>.
COPYRIGHT
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
The full documentation for chmod is maintained as a Texinfo manual. If the info and chmod programs are properly installed at your site,
the command
info chmod
should give you access to the complete manual.
chmod (coreutils) 4.5.3 February 2003 CHMOD(1)