You can't write to the source directory (cannot unlink the old reference)
You can't write to the target directory (cannot link the new reference)
You can't read the source file (read to copy if moving filesystem)
In addition to the output requested by Scrutinizer, can you list the file you want to move with ls -ld lynx*test*
It might also be worth dropping the trailing /. from the target directory on the move, so it becomes mv lynx*test* $clftparchive only.
It would be wise to check that this directory exists before trying to write to it with:-
I'm sure we can help you work this out,
Robin
Can anyone help explain the "s" in the below permissions example. I was reading about the "sticky bit" (t) but I am a little confused.
On file "test"
wolf% chmod 4777 test
wolf% ls -l
total 4
drwx------ 2 john staff 512 Mar 19 21:34 nsmail
-rwsrwxrwx 1 john staff ... (2 Replies)
Hi everyone, I'm looking for some information concerning Unix permissions. I am new to Unix and am doing research for a graduate class. Given the permissions below, can anyone give me five unique exploits that would be available to a hacker/cracker given this configuaration?
-rw-rw-rw- 1... (1 Reply)
I saved a perl code in xemacs. I used an xterminal to execute it but unix said that I don't have permission. I saved the files in my home directory. How do I change the permission. This is hat unix said:
-ksh: ./names.pl: cannot execute (5 Replies)
Hey,
We've got quite a strange problem on our hands here. We are running an HP 9000/800 B.11.00.
I've just created a new group in /etc/group which i called, let's say newgroup . Then I added 4 users to the group, namely user1, user2, user3, user4 . The command grpchk shows no strange things... (4 Replies)
Hi,
I am a Unix Admin. I have to give the permissions to a user for creating new file in a directory in HP-Ux 11.11 system since he cannot able to create a new file in the directory.
Thanks in advance.
Mike (3 Replies)
My /tmp is set with the following permissions (777) and a 't' at the end.
My umask is set to 022.
When I create a directory under /tmp (tmp/xx) it gets created as 755
as expected.
Yet when I create a file within that directory (/tmp/xx/yy) the permissions
are not 755 they are 644.
... (1 Reply)
Hi, I am creating a ksh script to search for a string of text inside files within a directory tree. Some of these file are going to be read/execute only. I know to use chmod to change the permissions of the file, but I want to preserve the original permissions after writing to the file. How can I... (3 Replies)
Hi,
I have noticed that on my Linux box there is a nice feature which make it impossible for specified member (owner, group or other) to have an given access if a member from which we would expect it more don't have that access.
So it is impossible to read file by all if others have set read... (3 Replies)
Hi guys,
i write the below script to make the user get to the directory that interesting. Now what I am trying is to check the permissions of the directory and if the directory exists to check the reading options.
echo "Please enter your desire folder directory ( \yourfolders) ?: \c"
... (9 Replies)
Discussion started by: mikerousse
9 Replies
LEARN ABOUT OPENDARWIN
mv
MV(1) BSD General Commands Manual MV(1)NAME
mv -- move files
SYNOPSIS
mv [-f | -i | -n] [-v] source target
mv [-f | -i | -n] [-v] source ... directory
DESCRIPTION
In its first form, the mv utility renames the file named by the source operand to the destination path named by the target operand. This
form is assumed when the last operand does not name an already existing directory.
In its second form, mv moves each file named by a source operand to a destination file in the existing directory named by the directory oper-
and. The destination path for each operand is the pathname produced by the concatenation of the last operand, a slash, and the final path-
name component of the named file.
The following options are available:
-f Do not prompt for confirmation before overwriting the destination path. (The -f option overrides any previous -i or -n options.)
-i Cause mv to write a prompt to standard error before moving a file that would overwrite an existing file. If the response from the
standard input begins with the character 'y' or 'Y', the move is attempted. (The -i option overrides any previous -f or -n options.)
-n Do not overwrite an existing file. (The -n option overrides any previous -f or -i options.)
-v Cause mv to be verbose, showing files after they are moved.
It is an error for either the source operand or the destination path to specify a directory unless both do.
If the destination path does not have a mode which permits writing, mv prompts the user for confirmation as specified for the -i option.
As the rename(2) call does not work across file systems, mv uses cp(1) and rm(1) to accomplish the move. The effect is equivalent to:
rm -f destination_path &&
cp -pRP source_file destination &&
rm -rf source_file
DIAGNOSTICS
The mv utility exits 0 on success, and >0 if an error occurs.
SEE ALSO cp(1), rm(1), symlink(7)COMPATIBILITY
The -n and -v options are non-standard and their use in scripts is not recommended.
STANDARDS
The mv utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A mv command appeared in Version 1 AT&T UNIX.
BSD July 9, 2002 BSD