02-04-2012
Parent directory was missing write permission.Thanks!
I thought parent directory permission would not matter for determining access level for inside directory.
![Confused Smilie](https://www.unix.com/images/smilies/confused.gif)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi ..
I am trying to deleta a file but i cant do the error i get is
rm: hs_pdref_custom_dict_PG1_out_76_out non-existent
but when i do ls it is listing the in the directory ...
please find the filed below....
-rw-r----- 1 tsta107 users 118011030 Dec 1 04:07... (13 Replies)
Discussion started by: arunkumar_mca
13 Replies
2. UNIX for Advanced & Expert Users
Version-Release number of selected component (if applicable):
==================================================================
root@server # cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 5)
root@server # uname -a
Linux server.integrityserver.net... (16 Replies)
Discussion started by: fed.linuxgossip
16 Replies
3. UNIX for Dummies Questions & Answers
I have more than 1 million files (No directories). rm -rf * did not work.
How do i delete all these files at a stretch in a single command? (9 Replies)
Discussion started by: sydney2008
9 Replies
4. Solaris
Morning all, I was running some deployment scripts on Friday night that kept failing because it prompted for a password for a user I was already sudo'd in as when trying to scp a file onto itself.
e.g.
on server 51.123.123.123 as sudo dlam
typing: scp testfile dlam@51.123.123.123:/tmp ... (5 Replies)
Discussion started by: dlam
5 Replies
5. Cybersecurity
User usrA creates dirA directory and runs chmod 777 on the directory. Can usrB issue another 777 on dirA? It appears the answer is no even if the usrA and usrB are part of the same group. I know this is a rare scenario but I just ran across it and found out that usrB receives an error when... (4 Replies)
Discussion started by: zlek131
4 Replies
6. Solaris
Hi All,
I am trying to uninstall jdk 1.5 from my Solaris 10 64 bit but some how was not successful.so tried to delete the folder of jdk from /usr but its throughing error as:
Unable to remove directory jdk: Read-only file system
Even I tried to create a dir in /usr but its not allowing me... (4 Replies)
Discussion started by: Pshah
4 Replies
7. UNIX for Dummies Questions & Answers
Hi,
My apologies if my query is already available on this forum but I am new and could not find.
I need a script to list all directories/sub directories and files with permissions/groups/owners. The script would run from home directory and should capture every directory. How do I do this?
... (4 Replies)
Discussion started by: 8709711
4 Replies
8. UNIX for Dummies Questions & Answers
I finally installed Chakra Linux and noticed whether I create or extract a file with 700, 755, 775 permissions a * sign is listed at the end of the filename:
$ ls -l bin/32
total 16440
-rwxr-xr-x 1 501 utmp 6321496 09.12.2013 04:02 bitcoind*
-rwxr-xr-x 1 501 utmp 10508613 09.12.2013 04:02... (10 Replies)
Discussion started by: Azrael
10 Replies
9. AIX
heapdump716960.1416296627.txt
heapdump716960.1416299494.txt
heapdump716960.1416302375.txt
trying to delete the above files
root@atec:/oratec/prodcomn/temp>rm heap*.*.txt
ksh: /usr/bin/rm: 0403-027 The parameter list is too long.
root@atec:/oratec/prodcomn/temp>rm heap*.txt... (2 Replies)
Discussion started by: filosophizer
2 Replies
10. Shell Programming and Scripting
Hi
My directory structure is as below.
dir1, dir2, dir3
I have the list of files to be deleted in the below path as below.
/staging/retain_for_2years/Cleanup/log $ ls -lrt
total 0
drwxr-xr-x 2 nobody nobody 256 Mar 01 16:15 01-MAR-2015_SPDBS2
drwxr-xr-x 2 root ... (2 Replies)
Discussion started by: prasadn
2 Replies
mkdir(2) System Calls Manual mkdir(2)
NAME
mkdir - make a directory file
SYNOPSIS
DESCRIPTION
The system call creates a new directory file named by path. The file permission bits of the new directory are initialized from mode, and
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 new directory's mode is cleared (see umask(2)).
The directory's owner ID is set to the process's effective-user-ID. If the set-group-ID bit of the parent directory is set, the direc-
tory's group ID is set to the group ID of the parent directory. Otherwise, the directory's group ID is set to the process's effective-
group-ID. The set-group-ID bit of the new directory is set to the same value as the set-group-ID bit of the parent directory.
Symbolic constants defining the access permission bits are found in the header and are used to construct the argument mode. The value of
the argument mode is the bitwise inclusive OR of the values of the desired permissions.
Read by owner.
Write by owner.
Execute (search) by owner.
Read by group.
Write by group.
Execute (search) by group.
Read by others (that is, anybody else).
Write by others.
Execute (search) by others.
Access Control Lists - HFS File Systems Only
On HFS file systems implementing access control lists, the directory is created with three base ACL entries, corresponding to the file
access permission bits (see acl(5)).
Access Control Lists - JFS File Systems Only
On JFS file systems that support access control lists, optional ACL entries are created corresponding to the parent directory's default ACL
entries. Also, the parent directory's default ACL entries are copied as the new directory's default ACL entries (see aclv(5)).
RETURN VALUE
returns one of the following values:
Successful completion.
Failure.
An error code is stored in
ERRORS
If fails, no directory is created and is set to one of the following values:
A component of the path prefix denies search permission.
The parent directory of the new directory denies write permission.
User's or group's disk quota block or inode limit
has been reached for this file system.
The named file already exists.
path points outside the process's allocated address space. The reliable detection of this error is implementation dependent.
An I/O error occurred while writing to the file system.
Too many symbolic links are encountered in translating the path name.
The maximum number of links to the parent directory,
would be exceeded.
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.
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 named file resides on a read-only file system.
AUTHOR
was developed by the University of California, Berkeley.
SEE ALSO
acl(2), chmod(2), setacl(2), stat(2), umask(2), acl(5), aclv(5), limits(5).
STANDARDS CONFORMANCE
mkdir(2)