04-08-2002
Stciky bits
Help!!
I am trying to give users the ability to manipulate a file via a script that was written but I don't want the users (group of Sterling) to have write permission (for fear that it'll get deleted by accident) when using regular shell commands. I'm thinking that this is accomplished via Sticky bits. I've searched the man pages along with my Unix in a nutshell book and can't really find what I'm looking for. I'm not sure if I put the sticky bit at the file, script or directory level or all of the above. Can you guys take a look and see what I'm doing wrong?
Additionally, I am on AIX 4.3 (if that makes a difference)
The file I am wanting to protect Except when they run the script:
-rw-r--r-- 1 cdunix sterling 34918 Apr 08 09:49 univfile
The permissions on that directory are:
drwxrws--- 2 cdunix sterling 512 Apr 08 10:18 flatfile
Current permissions of the script that the user would be running:
-rwSrwsrw- 1 cdunix sterling 9174 Apr 08 09:47 addchgdel.sh
The permissions on that directory are:
drwxr-sr-x 5 cdunix sterling 1536 Apr 08 10:07 utils
Thanks in advance for taking a look!
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
I was wondering if anyone can tell me how to change 24 bits depth display to 8 bits depth display for Sun Ultra1, running Solaris 8? THANKS in advance. I think that the command is ffbconfig, but it has nothing about depth. (4 Replies)
Discussion started by: larry
4 Replies
2. AIX
Hello there:
I know that exist a procedure to convert an OS using 32bits kernel to 64 bits kernel. But, exist a procedure to convert an OS using 64bits to 32 bits kernel?
Please help me.
Regards. (2 Replies)
Discussion started by: GEIER
2 Replies
3. Post Here to Contact Site Administrators and Moderators
My bits count is increasing and decreasing frequently. I haven't get infractions at present. But my bits count is getting increasing and decreasing frequently. Previously it was not like that. May know the reasons please?
Thanks in Advance. (3 Replies)
Discussion started by: thillai_selvan
3 Replies
4. UNIX for Dummies Questions & Answers
people i have a problem i have a 32 bits sparc processor, and solaris 64 bits processor, i install a oracle data base 64 bits, but my oracle will not run because my processor is from 32 bits this is ok??, i know if i have x86 i cannot install a 64 bits operatin system in a 32 bits processor.
... (0 Replies)
Discussion started by: enkei17
0 Replies
5. What is on Your Mind?
Ten movies have been nominated as best motion picture by the International Press Academy, presentation of the 2012 Satellite Awards will be held on 16th December at Los Angeles, CA.
Place your bits here on one of the below nominated movie of your choice:-
Argo
... (0 Replies)
Discussion started by: Yoda
0 Replies
6. What is on Your Mind?
Hi Friends..
Can anyone explain me the usage of bits....
I am unable to understand .....
I've moved this to a more appropriate forum on the board. Please consider where you are posting. (2 Replies)
Discussion started by: bharat1211
2 Replies
7. Post Here to Contact Site Administrators and Moderators
Hi there admins/moderators,
I've just found that all my bits have vanished... both Savings and Checking accounts are showing '0' as the balance. I initially thought it was nefarious carry-on to blame but I can't see any evidence of a transfer out. Then I figured that bits had been... (3 Replies)
Discussion started by: Smiling Dragon
3 Replies
STRMODE(3) BSD Library Functions Manual STRMODE(3)
NAME
strmode -- convert inode status information into a symbolic string
LIBRARY
Utility functions from BSD systems (libbsd, -lbsd)
SYNOPSIS
#include <bsd/string.h>
void
strmode(mode_t mode, char *bp);
DESCRIPTION
The strmode() function converts a file mode (the type and permission information associated with an inode, see stat(2)) into a symbolic
string which is stored in the location referenced by bp. This stored string is eleven characters in length plus a trailing NUL.
The first character is the inode type, and will be one of the following:
- regular file
b block special
c character special
d directory
l symbolic link
p fifo
s socket
w whiteout
? unknown inode type
The next nine characters encode three sets of permissions, in three characters each. The first three characters are the permissions for the
owner of the file, the second three for the group the file belongs to, and the third for the ``other'', or default, set of users.
Permission checking is done as specifically as possible. If read permission is denied to the owner of a file in the first set of permis-
sions, the owner of the file will not be able to read the file. This is true even if the owner is in the file's group and the group permis-
sions allow reading or the ``other'' permissions allow reading.
If the first character of the three character set is an ``r'', the file is readable for that set of users; if a dash ``-'', it is not read-
able.
If the second character of the three character set is a ``w'', the file is writable for that set of users; if a dash ``-'', it is not
writable.
The third character is the first of the following characters that apply:
S If the character is part of the owner permissions and the file is not executable or the directory is not searchable by the owner, and
the set-user-id bit is set.
S If the character is part of the group permissions and the file is not executable or the directory is not searchable by the group, and
the set-group-id bit is set.
T If the character is part of the other permissions and the file is not executable or the directory is not searchable by others, and the
``sticky'' (S_ISVTX) bit is set.
s If the character is part of the owner permissions and the file is executable or the directory searchable by the owner, and the set-
user-id bit is set.
s If the character is part of the group permissions and the file is executable or the directory searchable by the group, and the set-
group-id bit is set.
t If the character is part of the other permissions and the file is executable or the directory searchable by others, and the ``sticky''
(S_ISVTX) bit is set.
x The file is executable or the directory is searchable.
- None of the above apply.
The last character is a plus sign ``+'' if any there are any alternate or additional access control methods associated with the inode, other-
wise it will be a space.
SEE ALSO
chmod(1), find(1), stat(2), getmode(3), setmode(3)
HISTORY
The strmode() function first appeared in 4.4BSD.
BSD July 28, 1994 BSD