Permissions take a different meaning for directories. Here's what they mean:
read determines if a user can view the directory's contents, i.e. do ls in it.
write determines if a user can create new files or delete file in the directory. (Note here that this essentially means that a user with write access toa directory can delete files in the directory even if he/she doesn't have write permissions for the file! So be careful with this.)
execute determines if the user can cd into the directory.
Hello all,
I have gone through the search and looked at posting about idle users and killing processes. Here is my question I would like to kill an idle user ( which I can do) but how can I asure that all of his process is also killed whit out tracing his inital start PID. I have tried this on a... (4 Replies)
Hi All,
I have an issue that's eating my head for few days. I would appreciate if anyone could help me out in this to resolve this.
In Solaris 8 container I am facing the below issue.
As oracle user when I do ls -l in /dboracle mountpoint getting permission denied error messages.
$ ls... (3 Replies)
i used function fork().
so i made two process.
parent process accepted socket fd and writing to shared memory.
then now. how can child process share parent's socket fd?
is this possible?
Thanks in advance (1 Reply)
If I have a file/folder that a user does not have permission to and I try to rename it, it removes the entire parent folder. At that point it is only visible in a ls. (Not a ls -l, file, more, cd). It happens on every filesystem. This is Aix 5.3
$ cd test
$ ls -la
total 0
drwxr-xr-x 2 root ... (4 Replies)
1. The problem statement, all variables and given/known data:
I need to make an program that in a loop creates one parent and five children with fork(). The problem i'm trying to solve is how to delete the parent and child of the childīs process.
2. Relevant commands, code, scripts,... (0 Replies)
Hi everyone
i am very new to linux , working on bash shell.
I am trying to solve the given problem
1. Create a process and then create children using fork
2. Check the Status of the application for successful running.
3. Kill all the process(threads) except parent and first child... (2 Replies)
Kindly help below command details in UNIX.
1.What is the Unix command to see parent and child directory details starting from root directory in tree structure using LS-LRT or any other way
2.What is the Unix command to see parent and child directory details starting from root directory in... (2 Replies)
Asking about the permission inherit from the parent directory
I am running the web app with tomcat8, I did use umask 007 to set permission for folder which enable the sub files and folder inherit the permission from the parent directory, I was successful which some directories but the directories... (1 Reply)
Asking about the permission inherit from the parent directory
I am running the web app with tomcat8, I did use umask 007 to set permission for folder which enable the sub files and folder inherit the permission from the parent directory, I was successful which some directories but the directories... (2 Replies)
Discussion started by: janecaongoc
2 Replies
LEARN ABOUT MOJAVE
sticky
STICKY(7) BSD Miscellaneous Information Manual STICKY(7)NAME
sticky -- sticky text and append-only directories
DESCRIPTION
A special file mode, called the sticky bit (mode S_ISVTX), is used to indicate special treatment for directories. It is ignored for regular
files. See chmod(2) or the file <sys/stat.h> for an explanation of file modes.
STICKY DIRECTORIES
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 super-user. This feature is usefully applied to directories such as /tmp
which must be publicly writable but should deny users the license to arbitrarily delete or rename each others' files.
Any user may create a sticky directory. See chmod(1) for details about modifying file modes.
HISTORY
A sticky command appeared in Version 32V AT&T UNIX.
BUGS
Neither open(2) nor mkdir(2) will create a file with the sticky bit set.
BSD June 5, 1993 BSD