See "man 2 chmod" for an explanation of the sticky bit on individual files. It's more about caching than permissions.
The sticky bit does have a use for directories in some O/S.
The file myfile can be read by anyone in mygroup but the sticky bit on the directory stops them deleting the file with error "not owner".
Try it. Not all O/S behave the same way.
A less complicated way to protect a file is to own the directory and the file and only allow write access to yourself. In this example users in your group can see the file and its contents but not make changes.
Last edited by methyl; 09-17-2009 at 11:18 AM..
Reason: layout - was too wide
I have a questions, whose answer may be very obvious:
Of what use is the sticky-bit permission on a Unix system?
I have looked at the chmod(1) man page on our HP-UX playground
system, and haven't been given much explanation:
Add or delete the save-text-image-on-file-
execution (sticky... (3 Replies)
I have a script that I want to be able to let user 'wcs1234' execute it, but when it runs, it will do so under the higher authority of 'cdunix'. It is my understanding that I accomplish this with a sticky bit. I have tried every variation of this but am unable to get this to work.
my script is... (2 Replies)
I have the sticky bit set on my /tmp directory, but users are still able to remove files that are not owned by them. Does the /etc/group file get invloved in securing these files ?? (1 Reply)
Hi,
could anyone please send me a link to learn/ know more about sticky bits? I am still not clear on the application of using a sticky bits.
Thanks for your help.
Regards,
UP (3 Replies)
Hi ,
I am having file permision as
drwxrwsr_x
I kwo for deleting a file in the diretory i need w permsion as well ..
Say if i am having the permsion as
drwxrwsrwx - wil any one can delete the files in the directory ..
And one more question what is the s doing there ..... (2 Replies)
HI
What is sticky bit?
how can be see if the sticky bit for file is set?
WHat is meaning of sticky bit set on Directory?
What is the syntax to set the sticky bit? With example
Thanks (10 Replies)
Hi,
I understand the purpose of sticky bit on directories. But I am not very clear about what the sticky bit do on a file.
Can any one explain me in detail and with example please.
Thanks in advance. (1 Reply)
as far as i understand, if sticky bit is set on a directory, the files created under tht directory cannot be deleted by ordinary user...
but we can do ths by permission itself,,, tht's assign only read permission to tht dirrectory
wht 's the difference? (1 Reply)
Discussion started by: udtyuvaraj
1 Replies
LEARN ABOUT BSD
chmod
CHMOD(1) General Commands Manual CHMOD(1)NAME
chmod - change mode
SYNOPSIS
chmod [ -Rf ] mode file ...
DESCRIPTION
The mode of each named file is changed according to mode, which may be absolute or symbolic. An absolute mode is an octal number con-
structed from the OR of the following modes:
4000 set user ID on execution
2000 set group ID on execution
1000 sticky bit, see chmod(2)
0400 read by owner
0200 write by owner
0100 execute (search in directory) by owner
0070 read, write, execute (search) by group
0007 read, write, execute (search) by others
A symbolic mode has the form:
[who] op permission [op permission] ...
The who part is a combination of the letters u (for user's permissions), g (group) and o (other). The letter a stands for all, or ugo. If
who is omitted, the default is a but the setting of the file creation mask (see umask(2)) is taken into account.
Op can be + to add permission to the file's mode, - to take away permission and = to assign permission absolutely (all other bits will be
reset).
Permission is any combination of the letters r (read), w (write), x (execute), X (set execute only if file is a directory or some other
execute bit is set), s (set owner or group id) and t (save text - sticky). Letters u, g, or o indicate that permission is to be taken from
the current mode. Omitting permission is only useful with = to take away all permissions.
When the -R option is given, chmod recursively descends its directory arguments setting the mode for each file as described above. When
symbolic links are encountered, their mode is not changed and they are not traversed.
If the -f option is given, chmod will not complain if it fails to change the mode on a file.
EXAMPLES
The first example denies write permission to others, the second makes a file executable by all if it is executable by anyone:
chmod o-w file
chmod +X file
Multiple symbolic modes separated by commas may be given. Operations are performed in the order specified. The letter s is only useful
with u or g.
Only the owner of a file (or the super-user) may change its mode.
SEE ALSO ls(1), chmod(2), stat(2), umask(2), chown(8)7th Edition May 22, 1986 CHMOD(1)