I am trying to automate the movement and renaming of a number of files in a directory. I am using the 'mv' command as I do not have access to 'rename'. I have the following scripted
Code:
FILES=$(ls /transfer/move/sys/mail/20130123/)
if [ ! -z "${FILES}" ] ; then
for i in ${FILES} ; do
mv /transfer/move/sys/mail/20130123/${FILES} /transfer/archive/sys/mail/20130123/MYFILENAME_`date +%Y%m%d%M%S00`.dat ; done
fi
which works perfectly when there is only one file in the directory, but when there are multiple files I get the following error
Greetings,
I know i can use the mv command to move and rename one file. How can I do this with multiple files?
example
pic01.bmp to pic0001.bmp
how can i perform this function on an entire directory of sequential files and keep them in sequence?
Hints, suggestions are most welcome:)
... (1 Reply)
Hi All,
Being new to scripting I am facing a new situation. We have an application that generates a file lets say dumpfile for each user under the users home directory when they execute the application. This is quite a huge file and imagine having that for over 40 users on a daily basis. The... (1 Reply)
So I am not sure if this should go in the shell forum or in the beginners. It is my first time posting on these forums.
I have a directory, main_dir lets say, with multiple sub directories (one_dir through onehundred_dir for example) and in each sub directory there is a test.txt. How would one... (2 Replies)
Hi,
I have 500 directories each with multiple data files inside them. The names are sort of random. For example, one directory has files named e_1.dat, e_5.dat, e_8.dat, etc. I need to move the files to a single directory and rename them all in numerical order, from 1.dat to 1000(or some... (1 Reply)
Dears,
I need your help!
I got a problem and found some workaround solution but I donno how to realize it.
I have a number of files (about 300 each day) and I need them to be renamed. All these files has fixed number of letters and name looks like this one:... (7 Replies)
Hey, I'm kinda new to the shell scripting and I don't wanna mess things up yet :)
Looking for a solution to the following:
I need to move all the files like "filename.failed.dateandtime" to another directory also renaming them "filename.ready". I can't figure how to do this with multiple files... (4 Replies)
I am a biologist and using an program on a computer cluster that generates a lot of data. The program creates a directory named
ExperimentX (where X is a number) that contains files "out.pdb" and "log.txt". I would like to create a script that renames the out.pdb file to out_ExperimentX.pdb (or... (1 Reply)
Hello,
I would like to rename all available files in a directory from Filename to Filename_Normal.
I tried to use below script but it is giving some error:
#!/bin/sh
for i in `ls`
do
echo Changing $i
mv $i $i_Normal
done
Error received:
Usage: mv src target
or: mv ... (10 Replies)
I have a directory full of directories, say called A B C D E ....
In each of these directories there are files called 1.dsp 2.dsp 3.dsp ..... along with others (with different extensions)
I need to go through each of these directories and move the dsp file to another folder, but with the name now... (6 Replies)
Hey guys,
ive been working on this for about 2hrs now - without any solution.
At first I need to say I dont have skills in linux bash scripting, but I tried to use some codesnippets and manuals from google.
What I want to do:
I have different folders including 2 different filestypes with... (15 Replies)
Discussion started by: peter1337
15 Replies
LEARN ABOUT OSX
rename
RENAME(2) BSD System Calls Manual RENAME(2)NAME
rename -- change the name of a file
SYNOPSIS
#include <stdio.h>
int
rename(const char *old, const char *new);
DESCRIPTION
The rename() system call causes the link named old to be renamed as new. If new exists, it is first removed. Both old and new must be of
the same type (that is, both must be either directories or non-directories) and must reside on the same file system.
The rename() system call guarantees that an instance of new will always exist, even if the system should crash in the middle of the opera-
tion.
If the final component of old is a symbolic link, the symbolic link is renamed, not the file or directory to which it points.
CAVEATS
The system can deadlock if a loop is present in the file system graph. This loop takes the form of an entry in directory 'a', say 'a/foo',
being a hard link to directory 'b', and an entry in directory 'b', say 'b/bar', being a hard link to directory 'a'. When such a loop exists
and two separate processes attempt to perform 'rename a/foo b/bar' and 'rename b/bar a/foo', respectively, the system may deadlock attempting
to lock both directories for modification.
Whether or not hard links to directories are supported is specific to the underlying filesystem implementation.
It is recommended that any hard links to directories in an underlying filesystem should be replaced by symbolic links by the system adminis-
trator to avoid the possibility of deadlocks.
Moving or renaming a file or directory into a directory with inheritable ACLs does not result in ACLs being set on the file or directory. Use
acl(3) in conjunction with rename() to set ACLs on the file or directory.
RETURN VALUES
A 0 value is returned if the operation succeeds, otherwise rename() returns -1 and the global variable errno indicates the reason for the
failure.
ERRORS
The rename() system call will fail and neither of the argument files will be affected if:
[EACCES] A component of either path prefix denies search permission.
[EACCES] The requested operation requires writing in a directory (e.g., new, new/.., or old/..) whose modes disallow this.
[EDQUOT] The directory in which the entry for the new name is being placed cannot be extended because the user's quota of disk
blocks on the file system containing the directory has been exhausted.
[EFAULT] Path points outside the process's allocated address space.
[EINVAL] Old is a parent directory of new, or an attempt is made to rename '.' or '..'.
[EIO] An I/O error occurs while making or updating a directory entry.
[EISDIR] new is a directory, but old is not a directory.
[ELOOP] Too many symbolic links are encountered in translating either pathname. This is taken to be indicative of a looping sym-
bolic link.
[ENAMETOOLONG] A component of a pathname exceeds {NAME_MAX} characters, or an entire path name exceeds {PATH_MAX} characters.
[ENOENT] A component of the old path does not exist, or a path prefix of new does not exist.
[ENOSPC] The directory in which the entry for the new name is being placed cannot be extended because there is no space left on the
file system containing the directory.
[ENOTDIR] A component of either path prefix is not a directory.
[ENOTDIR] old is a directory, but new is not a directory.
[ENOTEMPTY] New is a directory and is not empty.
[EPERM] The directory containing old is marked sticky, and neither the containing directory nor old are owned by the effective
user ID.
[EPERM] The new file exists, the directory containing new is marked sticky, and neither the containing directory nor new are owned
by the effective user ID.
[EROFS] The requested link requires writing in a directory on a read-only file system.
[EXDEV] The link named by new and the file named by old are on different logical devices (file systems). Note that this error
code will not be returned if the implementation permits cross-device links.
CONFORMANCE
The restriction on renaming a directory whose permissions disallow writing is based on the fact that UFS directories contain a ".." entry.
If renaming a directory would move it to another parent directory, this entry needs to be changed.
This restriction has been generalized to disallow renaming of any write-disabled directory, even when this would not require a change to the
".." entry. For consistency, HFS+ directories emulate this behavior.
SEE ALSO open(2), symlink(7)STANDARDS
The rename() function conforms to IEEE Std 1003.1-1988 (``POSIX.1'').
4.2 Berkeley Distribution September 18, 2008 4.2 Berkeley Distribution