I have a script to ftp, archive and delete files. I used tar command to archive files from a list and then all files were removed from name1/name2/name2/.
Code:
find /name1/name2/name2/ -name "*.txt" -print > filelist.log
while read line
do
if [ ! -e "$tarfile" ]; then
tar cvf $tarfile $line
else
tar rvf $tarfile $line
fi
done < filelist.log
#
How to untar and move files back to name1/name2/name2/ ?
When I, or any other user, tar -xzvf file.tar.gz the resulting uncompressed directory/file has the owner:group of a user on my system, but not that of the user who untared it.
How can this be? Is there a .conf file for gnutar that I'm not aware of?
Details:
--> running RedHat 7.1
--> 45... (4 Replies)
Hi All
Can someone pls guide me if there any utility to compress file on windows & uncompress on vxworks
I tried as -
- compressed some folders on windows ... i created .tar ( to maintain directory structure ) and compressed to .gz format.
- on VxWorks i have uncompressed it to .tar... (1 Reply)
I am trying to put together a script that will check for the latest file in a directory then extract it. The extraction and the scheduling I can do, but am not sure how to get it to check for the latest file.
These files are uploaded every evening by an external party and the previous days files... (3 Replies)
Hi,
i want tar the files from one location and untar it to other location using single line.
Can any one help me
zip and unzip using single line command. (2 Replies)
I use red hat linux.
I have two linux server .
I want to use tar over ssh to tar and untar the file.
The server A , have IP 10.1.1.a ,there is dir a and contain files.
The server B have IP 10.1.1.b , there is dir b and contain file .
So, in above case ,how can I tar over ssh sunc that the file... (0 Replies)
Hi Guys,
I am facing a strange issue
while doing parallel (using & for background) scp/untar operation from my unix box to multiple unix boxes...
I am getting
tar : unexpected EOF in archive error
the code is as follows.,,,
for i in 10
do
sh -c "scp <command> ; ssh tar -xf <tar> -C... (4 Replies)
Hi Guys,
I am able to untar a tar.gz file. But it is again extracting the tar file to further child directory.
I even tried the below command to untar it to particular directory.
tar -zxvf gme_dly_sls_20120515035335.txt.tar.gz -C /sites/VSTAR/site/live/ftp/GMEUROPE
I am getting the below... (4 Replies)
I have a tar file hello.tar which is 95 GB.
hello.tar has many files and folders including some tar files as well.
I wish to create a new tar ball which should maintain only the folder structure of hello.tar and the tar ball within the hello.tar
So basically the idea is to untar... (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT BSD
link
LINK(2) System Calls Manual LINK(2)NAME
link - make a hard link to a file
SYNOPSIS
link(name1, name2)
char *name1, *name2;
DESCRIPTION
A hard link to name1 is created; the link has the name name2. Name1 must exist.
With hard links, both name1 and name2 must be in the same file system. Unless the caller is the super-user, name1 must not be a directory.
Both the old and the new link share equal access and rights to the underlying object.
RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
Link will fail and no link will be created if one or more of the following are true:
[ENOTDIR] A component of either path prefix is not a directory.
[EINVAL] Either pathname contains a character with the high-order bit set.
[ENAMETOOLONG] A component of either pathname exceeded 255 characters, or entire length of either path name exceeded 1023 characters.
[ENOENT] A component of either path prefix does not exist.
[EACCES] A component of either path prefix denies search permission.
[EACCES] The requested link requires writing in a directory with a mode that denies write permission.
[ELOOP] Too many symbolic links were encountered in translating one of the pathnames.
[ENOENT] The file named by name1 does not exist.
[EEXIST] The link named by name2 does exist.
[EPERM] The file named by name1 is a directory and the effective user ID is not super-user.
[EXDEV] The link named by name2 and the file named by name1 are on different file systems.
[ENOSPC] The directory in which the entry for the new link is being placed cannot be extended because there is no space left on the
file system containing the directory.
[EDQUOT] The directory in which the entry for the new link is being placed cannot be extended because the user's quota of disk blocks
on the file system containing the directory has been exhausted.
[EIO] An I/O error occurred while reading from or writing to the file system to make the directory entry.
[EROFS] The requested link requires writing in a directory on a read-only file system.
[EFAULT] One of the pathnames specified is outside the process's allocated address space.
SEE ALSO symlink(2), unlink(2)4th Berkeley Distribution August 26, 1985 LINK(2)