02-06-2014
To the OP:
To exec a file, not only must it have the executable mode/permissions bit set, but so must all of the directories leading to it. Have you confirmed that bin, bin/32, and the directory components leading to the the current working directory (inclusive) all have the execute bit enabled?
Regards,
Alister
These 2 Users Gave Thanks to alister For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
I need your help with this problem.
I have my own ftp server implemented in java. If I start it as root it is successfully binded to port 21 and everything works. Now I want to run it as non-root user, but for binding to port 21 it needs root rights. How to solve it?
I alrady try... (3 Replies)
Discussion started by: giorgione
3 Replies
2. Shell Programming and Scripting
thi is (10 Replies)
Discussion started by: angelina
10 Replies
3. Solaris
Hello.
I am trying to run xclock on newly built solaris box - These are the steps I followed:
# DISPLAY=localhost:0.0
# export DISPLAY
# xclock
xclock: not found
# cd /usr/openwin/bin
# ./xclock
Error: Can't open display: localhost:0.0
#
Please suggest, what am i doing wrong?
Thank... (27 Replies)
Discussion started by: panchpan
27 Replies
4. Shell Programming and Scripting
i have some 700 files of the same pattern differing only in their datestamp. below some of the files.
i want to tar them all into one tar file.but the below normal command is telling me "arg list too long"
tar -cvf Archive1.tar CurrentCollectorMeterReadBackup*
also i tried the below... (6 Replies)
Discussion started by: ali560045
6 Replies
5. Cybersecurity
User usrA creates dirA directory and runs chmod 777 on the directory. Can usrB issue another 777 on dirA? It appears the answer is no even if the usrA and usrB are part of the same group. I know this is a rare scenario but I just ran across it and found out that usrB receives an error when... (4 Replies)
Discussion started by: zlek131
4 Replies
6. Cybersecurity
Hello,
I'm running rhel6 64bit. Accidentally I ran % chmod -R 777 /etc and after that I have a problem to do 'su' or 'sudo'. When I did sudo it complained that /etc/sudoers has 777 while it should be 0440. I changed that and also restored right permission for:
-rw-r--r-- 1 root root 1966 May 19... (2 Replies)
Discussion started by: susja
2 Replies
7. Shell Programming and Scripting
i have four files that have 777 permission
find /var/tttt/ -type f -perm 0777
/var/ttt/1
/var/ttt/2
/var/ttt/3
/var/ttt/4
if any file other than above 4 have 777 permission then move that file to /garbage/yyyy-mmm-dd . Also email me that this have abcd have 777 permission. (6 Replies)
Discussion started by: learnbash
6 Replies
8. AIX
Hi
I'm logged in to an AIX box now and we need to do an audit on this box.
cbssapr01:# pwd
/
Which command will show all the files and directories owned by root user with permissions as 777 ? (8 Replies)
Discussion started by: newtoaixos
8 Replies
9. Solaris
Hi,
I have an 'empty' directory 'tmp' of which I am the owner and 777 permission. But when I try to delete the directory using rmdir or rm command, it gives error.
Command prompt snapshot:
=> uname
SunOS
... (4 Replies)
Discussion started by: platinum81
4 Replies
10. Solaris
Hi,
I work as an Oracle Technical consultant (mainly DBA related), and I have used ZFS snapshots on previous projects which has helped me a great deal. I often take snapshots before doing some dev work, and then I can roll it back if I want to start again, or if it goes pear shaped!!
I have... (4 Replies)
Discussion started by: AndyG
4 Replies
LEARN ABOUT ULTRIX
sticky
sticky(8) System Manager's Manual sticky(8)
Name
sticky - executable files with persistent text
Description
The sticky bit (file mode bit 01000), is used to indicate special treatment for certain executable files and directories.
While the sticky bit, mode 01000 is set on a sharable executable file, the text of that file will not be removed from the system swap area.
Thus the file does not have to be fetched from the file system upon each execution. As long as a copy remains in the swap area, the origi-
nal text cannot be overwritten in the file system, nor can the file be deleted. Directory entries can be removed so long as one link
remains.
Sharable files are made by the and options of
To replace a sticky file that has been used, clear the sticky bit with and execute the old program to flush the swapped copy. This can be
done safely even if others are using it. Overwrite the sticky file. If the file is being executed by any process, writing will be pre-
vented. It suffices to simply remove the file and then rewrite it, being careful to reset the owner and mode with and Set the sticky bit
again.
A directory whose sticky bit is set becomes an append-only directory, or, more accurately, a directory in which the deletion of files is
restricted. A file in a sticky directory may only be removed or renamed by a user if the user has write permission for the directory and
the user is the owner of the file, the owner of the directory, or the superuser. This feature is usefully applied to directories such as
which must be publicly writeable but should deny users the license to arbitrarily delete or rename each others' files.
Restrictions
Only the superuser can set the sticky bit.
See Also
chmod(2)
RISC sticky(8)