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.
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
unlink(2) System Calls Manual unlink(2)
NAME
unlink - remove directory entry; delete file
SYNOPSIS
DESCRIPTION
The system call removes the directory entry named by the path name pointed to by path.
When all links to a file have been removed and no process has the file open, the space occupied by the file is freed and the file ceases to
exist. If one or more processes have the file open when the last link is removed, only the directory entry is removed immediately so that
processes that do not already have the file open cannot access the file. After all processes close their references to the file, if there
are no more links to the file, the space occupied by the file is then freed and the file ceases to exist.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
is set to indicate the error.
ERRORS
If fails, is set to one of the following values:
Search permission is denied for a component of the path prefix.
Write permission is denied on the directory containing the link to be removed.
The process does not have read/write access permission to the parent
directory.
The entry to be unlinked is the mount point for a mounted file system.
path points outside the process's allocated address space. The reliable detection of this error is implementation 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 named file does not exist (for example,
path is null or a component of path does not exist).
A component of the path prefix is not a directory.
The directory containing the file to be removed
has the sticky bit set and neither the containing directory nor the file to be removed are owned by the effective user ID.
The named file is a directory and
the effective user ID is not a user with appropriate privileges. Some file systems return this error whenever the named file
is a directory, regardless of the user ID.
The directory entry to be unlinked is part of a read-only file system.
The entry to be unlinked is the last link to a pure procedure
(shared text) file that is being executed.
WARNINGS
If is used on a directory that is not empty (contains files other than and the directory is unlinked, the files become orphans, and the
directory link count is left with an inaccurate value unless they are linked by some other directory.
If is used on a directory that is empty (contains only the files and the directory is unlinked, but the parent directory's link count is
left with an inaccurate value.
In either of the above cases, the file system should be checked using (see fsck(1M)). To avoid these types of problems, use instead (see
rmdir(2)).
SEE ALSO
rm(1), close(2), link(2), open(2), rmdir(2), remove(3C), privileges(5).
STANDARDS CONFORMANCE
unlink(2)