$x is the target, where the link points to.
The target should exist. The link is implicitly generated by the ln; you must explicitly generate it for a test.
Would I be correct in assuming that find doesn't bother recursivley searching down sim links. (It doesn't seem to so I guess it doesn't!!!) Is there anyway to make it do so? (3 Replies)
I have been experimenting with rsync as a scriptable backup option, reading various example and tips pages, including Time Machine for every Unix out there - IMHO
That page seems to describe the exact behavior I want: The ability to make a "full backup" snapshot regularly, but with rsync... (0 Replies)
Hello
A new file is created every day with the date appended to the end of a name. We are using Autosys to run jobs which watches for the file and runs jobs. But Autosys does not have the capability to figure out the current date.
I tried creating a symlink like this
ln -s... (1 Reply)
Does anybody know how to make symbolic links for multiple files simultaneously?
Often times I need make symbolic links for multiple files with some common pattern (just like "*.jpg"). Is there a way to avoid making symbolic link for each of them one by one...
Thank you! (6 Replies)
Hi
i need to install a software into a zone, and this kind of software needs to have a file who is linked into /dev.
But it is not possible to create a link into /dev nor create a file into it.
-bash-3.00# ln -s /tmp/testfile /dev/
ln: cannot create /dev//testfile: Permission denied... (2 Replies)
I have a problem with tar. Taring a folder with a lot of contents, causes the tar to contain hard links to some files, seen with the same name but 0 in size.
The hard links don't exist in the first place. How can I prevent that from happening?
I am using the -T option with either -n or... (2 Replies)
Hi,
I want to run a script over a series of files with the names :
Sample_1.sorted.bam
Sample_2.sorted.bam
Sample_3.sorted.bam
How can I specify it in my script. Thanks a lot in advance. (3 Replies)
Hi. Can somebody tell me if there's a way of creating a symbolic link from a directory on one filesystem to that on another that will allow a find command that doesn't use the -L param to locate a particular file under that new 'linked' dir. With a normal sym link the find command on that... (6 Replies)
Discussion started by: user052009
6 Replies
LEARN ABOUT HPUX
rename
rename(2) System Calls Manual rename(2)NAME
rename - change the name of a file
SYNOPSIS DESCRIPTION
The system call causes the source file to be renamed to target. If target exists, it is first removed. Both source and target must be of
the same type (that is, either directories or nondirectories), and must reside on the same file system.
If target can be created or if it existed before the call, guarantees that an instance of target will exist, even if the system crashes in
the midst of the operation.
If the final component of source is a symbolic link, the symbolic link is renamed, not the file or directory to which the symbolic link
points.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
Neither file is affected. is set to indicate the error.
ERRORS
If fails, is set to one of the following values.
[EACCES] A component of either path prefix denies search permission.
[EACCES] The requested link requires writing to a directory without write permission.
[EBUSY] target or source is an existing directory that is the mount point for a mounted file system.
[EDQUOT] User's disk quota block or inode limit has been reached for this file system.
[EEXIST] target is a directory and is not empty.
[EFAULT] source or target points outside the allocated address space of the process. Reliable detection of this error is
implementation dependent.
[EINVAL] source is a parent directory of target, or an attempt is made to rename the or directory.
[EISDIR] target is a directory, but source is not.
[ELOOP] Too many symbolic links were encountered in translating either path name.
[ENAMETOOLONG] A component of either path name exceeds bytes while is in effect, or the entire length of either path name exceeds
bytes.
[ENOENT] A component of the source path does not exist, or a path prefix of target does not exist.
[ENOSPC] The destination directory cannot be extended because of a lack of space on the file system containing the directory.
[ENOTDIR] A component of either path prefix is not a directory.
[ENOTDIR] source is a directory, but target is not.
[EPERM] The directory containing source has the sticky bit set, and neither the containing directory nor the source are owned
by the effective user ID.
[EPERM] The target file exists, the directory containing target has the sticky bit set, and neither the containing directory
nor the target are owned by the effective user ID.
[EROFS] The requested link requires writing in a directory on a read-only file system.
[EXDEV] The paths named by source and target are on different logical devices (file systems).
AUTHOR
was developed by the University of California, Berkeley.
SEE ALSO open(2).
STANDARDS CONFORMANCE rename(2)