It seems the admins have done that for me. I didn't realize that when I posted.
What remains is the problem of making everything in the directory group-writable automatically. I seem to remember that that's what I kept on forgetting when editing group web pages in the past (I just haven't done it in a while).
Is there a way to set the umask for a particular directory or something? Maybe along the lines of:
But how do I get that excecuted every time I log on to work on group web pages, but not when I log on to work on my personal web page? .bashrc won't work... It would have to be read after I cd to the directory :-/
Hello,
Another newbie here and here is my dilemma. I created an account for me on Solaris 8 and I added myself to the root group. But when I login using that account I am unable to do superuser tasks.. (add users, admintool, etc). What am I missing? Thanks in advance..
Andre (5 Replies)
Hi,
there is one strange situation with directory permissions that I run into every now and then, and now I face it a gain with a webserver.
Situation (example):
drwxrwsr-x 14 user www-data 4096 Jul 28 11:06 .
drwxr-xr-x 2 www-data www-data 4096 Jul 28 11:06 subdir
-rwxr-xr-x 1... (3 Replies)
Hi,
I'm in the process of writing a system (in Java) where a user can register to become a member of a website.
When they register, a collection of directories and files get created by the application.
For example if a user with the name 'fred' registered they would get the following
drwxr-xr-x... (0 Replies)
I was doing a little playing around with permissions on a 5.3 box in the office and wanted to make it so that it does not take root permission to delete a users home directory once they are deactivated or deleted in smit.
the default permissions are 755 with bin as both user and group
I noticed... (2 Replies)
Hi,
I've created a user named fwadmin, group named fwadmin and made the user belong to that group. I created the user and group using the 'User Manager' in Centos.
The user belongs to /etc/fw.Does this also mean that the group fwadmin belongs to /etc/fw. That is what I want.
But when I... (4 Replies)
I am a member of a few different user groups.
I would like to see what the difference is....
Can anyone tell me how to look at permissions side by side ?
We are using :
SunOS xxxxxx 5.10 Generic_127111-09 sun4u sparc SUNW,Sun-Fire-V440
Thanks ! (10 Replies)
Hi,
I am using Solaris 10 OS and Bash shell.Is there any way can we automate User creation and setting passwords through a script or any freeware tool.
Advance thanks for your response. (1 Reply)
I have a user who has had an id change. His old id was xl00 his new id b000999. Both id's are in group bauser. The user now cannot access his old files even though he is in the same group and permissions seem to be ok. See below, first 2 files he can't see, second two are no problem.
... (2 Replies)
Discussion started by: dw82199
2 Replies
LEARN ABOUT CENTOS
mkdir
MKDIR(2) Linux Programmer's Manual MKDIR(2)NAME
mkdir - create a directory
SYNOPSIS
#include <sys/stat.h>
#include <sys/types.h>
int mkdir(const char *pathname, mode_t mode);
DESCRIPTION
mkdir() attempts to create a directory named pathname.
The argument mode specifies the permissions to use. It is modified by the process's umask in the usual way: the permissions of the created
directory are (mode & ~umask & 0777). Other mode bits of the created directory depend on the operating system. For Linux, see below.
The newly created directory will be owned by the effective user ID of the process. If the directory containing the file has the set-group-
ID bit set, or if the file system is mounted with BSD group semantics (mount -o bsdgroups or, synonymously mount -o grpid), the new direc-
tory will inherit the group ownership from its parent; otherwise it will be owned by the effective group ID of the process.
If the parent directory has the set-group-ID bit set then so will the newly created directory.
RETURN VALUE
mkdir() returns zero on success, or -1 if an error occurred (in which case, errno is set appropriately).
ERRORS
EACCES The parent directory does not allow write permission to the process, or one of the directories in pathname did not allow search per-
mission. (See also path_resolution(7).)
EDQUOT The user's quota of disk blocks or inodes on the file system has been exhausted.
EEXIST pathname already exists (not necessarily as a directory). This includes the case where pathname is a symbolic link, dangling or
not.
EFAULT pathname points outside your accessible address space.
ELOOP Too many symbolic links were encountered in resolving pathname.
EMLINK The number of links to the parent directory would exceed LINK_MAX.
ENAMETOOLONG
pathname was too long.
ENOENT A directory component in pathname does not exist or is a dangling symbolic link.
ENOMEM Insufficient kernel memory was available.
ENOSPC The device containing pathname has no room for the new directory.
ENOSPC The new directory cannot be created because the user's disk quota is exhausted.
ENOTDIR
A component used as a directory in pathname is not, in fact, a directory.
EPERM The file system containing pathname does not support the creation of directories.
EROFS pathname refers to a file on a read-only file system.
CONFORMING TO
SVr4, BSD, POSIX.1-2001.
NOTES
Under Linux apart from the permission bits, only the S_ISVTX mode bit is honored. That is, under Linux the created directory actually gets
mode (mode & ~umask & 01777). See also stat(2).
There are many infelicities in the protocol underlying NFS. Some of these affect mkdir().
SEE ALSO mkdir(1), chmod(2), chown(2), mkdirat(2), mknod(2), mount(2), rmdir(2), stat(2), umask(2), unlink(2), path_resolution(7)COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2013-01-27 MKDIR(2)