Sponsored Content
Full Discussion: ACL confusion
Top Forums UNIX for Advanced & Expert Users ACL confusion Post 303005303 by hburnswell on Tuesday 17th of October 2017 01:10:51 AM
Old 10-17-2017
Thanks for the reply. No, this is not a system directory. It is 25TB of unstructured data.

I was unable to come up with a solution prior to needing it back online so I remounted the directory without the 'acl' option to avoid the permission confusion. I will need to address this in the next couple weeks and will update on the progress..

HB
 

8 More Discussions You Might Find Interesting

1. Cybersecurity

ACL

Hi all, I've just been handled the responsibility for a FTP-site. Having no experiens of UNIX at all. And now one of my users needs to have full access to the usr directory and all it's subdirectories, don't know why just trying to do what the boss tells me. The type of UNIX is FreeBSD and the... (4 Replies)
Discussion started by: -tri-
4 Replies

2. UNIX for Dummies Questions & Answers

ACL vs privileges

Hello genius..! what do y'all think of these questions...? help appreciated...! Access Control Lists and privileges.... # Why both file ACLs and user permissions/privileges (not to be confused with rights in ACLs) are used in Windows access control (why not just use one of these)? # In... (1 Reply)
Discussion started by: heroine
1 Replies

3. AIX

setting acl

Hi, I want to know how to set acl in aix via smitty and shell prompt, wheather we needs to install additional packages. (0 Replies)
Discussion started by: manoj.solaris
0 Replies

4. Shell Programming and Scripting

Need help to create ACL

Hi, I generated a script that will create the list of dir/sub-dir and will allow to create the same on diff server. this is what i have done : #!/bin/ksh # Script to migrate the directory between the two servers. # Ver 0.1 # Author Krishna. D # c - create and e - extract directory if ;... (1 Reply)
Discussion started by: krishnadvn
1 Replies

5. Linux

ACL

Hi, I want to know what does the "effective" comment means in the output of the getfacl and whether it has to do with the acl mask... thanks (0 Replies)
Discussion started by: Gartlar
0 Replies

6. Solaris

ACL

Can i get the synopsis for add multiple users in single command for ACL access for a directory or a file thanks in advance dinu (3 Replies)
Discussion started by: dinu
3 Replies

7. HP-UX

When did HP-UX have support for ACL?

Hello, I try to find what year HP-UX got support for ACL (Access Control List)? I know that HP-UX was the first Unix with ACL support, but it is very hard to find the information on when that occured. So anyone here know when that did happen? Any answers are appreciated, /eXpander (1 Reply)
Discussion started by: eXpander
1 Replies

8. UNIX for Advanced & Expert Users

Need assistance on ACL

Hi Friends, I went through the ACL threads that were posted in the past but none were matching to my requirement . Hence starting a new thread . Challenge : user : a group : Test1 user: b group: Test2 Say under user a i create dir /tmp/debug with the privilege of 755 and also... (3 Replies)
Discussion started by: leobreaker
3 Replies
mknod(2)							System Calls Manual							  mknod(2)

NAME
mknod() - make a directory, special, or ordinary file SYNOPSIS
DESCRIPTION
The system call creates a new file named by the path name pointed to by path. The mode of the new file is specified by the mode argument. Symbolic constants that define the file type and file access permission bits are found in the header file and are used to construct the mode argument. The value of the mode argument should be the bit-wise inclusive OR of the values of the desired file type, miscellaneous mode bits, and access permissions. See stat(5) for a description of the components of the file mode. The owner ID of the file is set to the effective-user-ID of the process. If the set-group-ID bit of the parent directory is set, the new file's group ID is set to the group ID of the parent directory. Otherwise, the new file's group ID is set to the effective-group-ID of the process. The file access permission bits of mode are modified by the process's file mode creation mask: for each bit set in the process's file mode creation mask, the corresponding bit in the file's mode is cleared (see umask(2)). In HFS file systems, the new file is created with three base access-control-list (ACL) entries, corresponding to the file access permission bits (see acl(5)). On JFS file systems that support access control lists, when creating a directory or regular file, optional ACL entries are created corresponding to the parent directory's default ACL entries (see aclv(5)). When creating a directory, the parent's default ACL entries are also copied as the new directory's default ACL entries. The dev argument is meaningful only if mode indicates a block or character special file, and is ignored otherwise. It is an implementa- tion- and configuration-dependent specification of a character or block I/O device. The value of dev is created by using the macro defined in The macro takes as arguments the major and minor device numbers, and returns a device identification number which is of type The value and interpretation of the major and minor device numbers are implementation-dependent. For more information, see mknod(5) and the System Administration manuals for your system. Only users having appropriate privileges can invoke for file types other than FIFO files. RETURN VALUE
returns the following values: Successful completion. Failure. The new file is not created. is set to indicate the error. ERRORS
If fails, is set to one of the following values. The directory in which path would be created denies write permission, mode is for a FIFO file and the caller does not have appropriate priv- ileges. A component of the path prefix denies search permission. The user's or group's disk quota block or inode limit has been reached for this file system. The named path already exists. The path argument points outside the process's allocated address space. The reliable detection of this error is imple- mentation dependent. Too many symbolic links were encountered in translating the path name. The length of the specified path name exceeds bytes, or the length of a component of the path name exceeds bytes while is in effect. The path argument is null. A component of the path prefix does not exist. Not enough space on the file system. A component of the path prefix is not a directory. The effective-user-ID of the process does not match that of a user who has appropriate privileges, and the file type is not FIFO special. The directory in which the file is to be created is located on a read-only file system. AUTHOR
was developed by AT&T and HP. SEE ALSO
mknod(1M), acl(2), chmod(2), exec(2), mkdir(2), setacl(2), umask(2), acl(5), aclv(5), mknod(5), stat(5), types(5). STANDARDS CONFORMANCE
mknod(2)
All times are GMT -4. The time now is 08:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy