Asking about the permission inherit from the parent directory
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 under the tomcat8/webapps did not inherit the permissions. Could you please suggest me other ways?
For example :
I set the permissions before running script to deploy the web app under tomcat8.
After running the script, it copy some files and directories to the folder1, folder2, backupfolder with the same permission with but it doesnt work with the tomcat8/webapps directory. Could anyone help me? Thank you!
Last edited by vbe; 11-14-2019 at 04:54 AM..
Reason: Typo
Hi, I'm new to unix -solaris.
I've just upgraded a third party software product and am testing
it to see if new files created in a test database directory were being created properly and they aren't. They're owned by the user that created the file, instead of poppa and the group of their files... (2 Replies)
In our file system, the SGID for a directory is set right now. Any new files created in this directory will automatically be assigned the same group from the parent directory.
Is there a way to inherit the file permission from the parent directory as well? The OS is Solaris 2.8.
Example:... (1 Reply)
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)
Hi there,
I want to restrict a users account to only a subdirectory, but it does not seem to be working.
For example
/dir1/dir2/dir3/dir4
user A is only allowed to do things in dir4. the permission is 777.
i've set the permissions to 700 on dir3, dir2, and dir1 to prevent them from... (3 Replies)
Hi folks,
I have an query that is let say i have to search in an xml file an tag that is <abcdef> now this xml file is at /opt/usr/local so one fastest way to achieve this is go to this location by cd /opt/usr/local and then do grep like this... grep -i abcdef but for this I must know the... (4 Replies)
Hi.
My example:
I have a filesystem /log. Everyday, log files are copied to /log. I'd like to set owner and permission for files and directories in /log like that
chown -R log_adm /log/*
chmod -R 544 /log/*It's OK, but just at that time. When a new log file or new directory is created in /log,... (8 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... (2 Replies)
Discussion started by: janecaongoc
2 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)