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 OPENSOLARIS
mkdir
mkdir(1) User Commands mkdir(1)NAME
mkdir - make directories
SYNOPSIS
/usr/bin/mkdir
/usr/bin/mkdir [-m mode] [-p] dir...
ksh93
mkdir [-p] [-m mode] dir...
DESCRIPTION
/usr/bin/mkdir
The mkdir command creates the named directories in mode 777 (possibly altered by the file mode creation mask umask(1)).
Standard entries in a directory (for instance, the files ".", for the directory itself, and "..", for its parent) are made automatically.
mkdir cannot create these entries by name. Creation of a directory requires write permission in the parent directory.
The owner-ID and group-ID of the new directories are set to the process's effective user-ID and group-ID, respectively. mkdir calls the
mkdir(2) system call.
setgid and mkdir
To change the setgid bit on a newly created directory, you must use chmod g+s or chmod g-s after executing mkdir.
The setgid bit setting is inherited from the parent directory.
ksh93
The mkdir built-in in ksh93 is associated with the /bin and /usr/bin paths. It is invoked when mkdir is executed without a pathname prefix
and the pathname search finds a /bin/mkdir or /usr/bin/mkdir executable. mkdir creates one or more directories. By default, the mode of
created directories is a=rwx minus the bits set in umask(1).
OPTIONS
/usr/bin/mkdir
The following options are supported by /usr/bin/mkdir:
-m mode This option allows users to specify the mode to be used for new directories. Choices for modes can be found in chmod(1).
-p With this option, mkdir creates dir by creating all the non-existing parent directories first. The mode given to intermediate
directories is the difference between 777 and the bits set in the file mode creation mask. The difference, however, must be at
least 300 (write and execute permission for the user).
ksh93
The following options are supported by the mkdir built-in in ksh93:
-m mode Set the mode of created directories to mode. mode is symbolic or octal mode as in chmod(1). Relative modes assume an initial
--mode=mode mode of a=rwx.
-p Create any missing intermediate pathname components. For each dir operand that does not name an existing directory, effects
--parents equivalent to those caused by the following command shall occur:
mkdir -p -m $(umask -S),u+wx
$(dirname dir) && mkdir [-m mode] dir
Where the -m mode option represents that option supplied to the original invocation of mkdir, if any. Each dir operand that
names an existing directory is ignored without error.
OPERANDS
The following operand is supported:
dir A path name of a directory to be created.
USAGE
See largefile(5) for the description of the behavior of mkdir when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
EXAMPLES
Example 1 Using mkdir
The following example:
example% mkdir -p ltr/jd/jan
creates the subdirectory structure ltr/jd/jan.
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of mkdir: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
EXIT STATUS
The following exit values are returned:
0 All the specified directories were created successfully or the -p option was specified and all the specified directories now exist.
>0 An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
/usr/bin/mkdir
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|Standard |See standards(5). |
+-----------------------------+-----------------------------+
ksh93
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |See below. |
+-----------------------------+-----------------------------+
|Standard |See standards(5). |
+-----------------------------+-----------------------------+
The ksh93 built-in binding to /bin and /usr/bin is Volatile. The built-in interfaces are Uncommitted.
SEE ALSO chmod(1), ksh93(1), rm(1), sh(1), umask(1), Intro(2), mkdir(2), attributes(5), environ(5), largefile(5), standards(5)SunOS 5.11 2 Nov 2007 mkdir(1)