03-06-2018
Quote:
Originally Posted by
anaigini45
The error gzip not found can be resolved by putting the full path to gzip.
However, the error "tar: cannot open /home/emoaigin/abc.sh" why does it happen?
And what is this error : "Tar: blocksize = 0; broken pipe?" ?
First off: i think RudiC is correct in his analysis as to where the errors come from. But the - real - problem is something completely different:
Try to think like an engineer does and solve problems like an engineer would do. You throw 20 commands together and expect them to work flawlessly hand in hand on first try. If that fails you ask us.
How about trying the procedure i showed you with a single file or a single (small) directory? Now you notice you have
gzip errors and correct that. Perhaps now it works. Now, on to the next more difficult problem. And so on....
The advantage this has is: whenever in this process an error comes up you understand immediately where it comes from, because the previous version was working. You put together a monstrous kludge of a command and then have no idea how to isolate the myriad of (maybe, maybe not) interdependent error conditions, some of which may (or maybe not?) corrected.
Instead of writing "the gzip error could be corrected" - why don't you just do it, run again and post what happens then?? In case all the other stuff would have worked the missing
gzip would still have caused the rest of the pipeline to fail and you would still get the same
tar-error because this is how
tar reacts to empty input. But why do we have to take interactions between different unrelated errors into account when you cannot be bothered to do anything on yourself to isolate the persistent errors?
A child would say "toilet isn't working" - and call for adult help. Adults would observe that the water system works in
this part of the house, but not in
that part. So they would analyse the pipe system and find out that
somewhere between here and there must be a problem. They might then proceed to correcting that problem.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I would like to back up several directories weekly using a cronjob.
I'm not experienced in UNIX, but I would start like this:
tar -cvf backup.tar dir1 dir2 dir3
Now if a file is being modified in the process it will result in an error.
How can I prevent this from happening and how can I... (5 Replies)
Discussion started by: jamesbond
5 Replies
2. UNIX for Dummies Questions & Answers
Say I want to transfer several dump files from a Solaris machine onto a Win2k machine for storage. It was suggested that I tar and gzip the dump files before doing so.
Is it completely necessary to use both of these utilities, or is it sufficient to compress multiple dump files into one gzip... (4 Replies)
Discussion started by: PSC
4 Replies
3. Shell Programming and Scripting
Hi,
I am facing a weired problem in my FTP script. I want to transfer multiple files from remote server to local server everyday, using mget * in my script. I also, want to send an email for successful or failed FTP. My script works for file transfer, but it don't send any mail. There is... (2 Replies)
Discussion started by: berlin_germany
2 Replies
4. UNIX for Dummies Questions & Answers
dears,
I have a folder containing huge no. of files, some of them are created on AUG 16, AUG 17 and AUG 18, for example.
All I want to do is tarring all the files created on a certain date, say AUG 18, in one tar file, only in one command line.
So, how to feed all the files created on a certain... (4 Replies)
Discussion started by: marwan
4 Replies
5. Shell Programming and Scripting
hi guys,
i'm totally new with Unix sripting and no idea how to do the scripting at all. My problem is that my boss asked me to do this:
1.) create a script that will tar or gzip the files in particular directory
eg:
i'm on my home directory and I need to tar/gzip the file in.. assuming... (1 Reply)
Discussion started by: montski
1 Replies
6. Shell Programming and Scripting
HI All,
Im encountering behaviour that is not correct for my requirements when I untar a file.
Im using the below command to tar up files from various folders to the ARCHIVE folder as below...
tar -cvf "$ARCHIVE_PATH"/"$dte_tar_filename" "$LOG_PATH" "$PROCESSED_PATH2" "$ERROR_PATH"
... (5 Replies)
Discussion started by: satnamx
5 Replies
7. UNIX for Dummies Questions & Answers
Hi I need help in tarring files up to four days old. I have been doing this:
find . -mtime -4|xargs tar -cvf mar4.tar
However, it seems like it's tarring everything but leaving those that are 4 days old and newer (which I want tarred and everything else not)
---------- Post updated at... (1 Reply)
Discussion started by: MIA651
1 Replies
8. Solaris
Hi,
I am trying to automate the process of fetching files from remote server to local server through sftp. I have the username and password for the remote solaris server. But I need to give password manually everytime i run the script.
Can anyone help me in automating the script such that it... (3 Replies)
Discussion started by: ssk250
3 Replies
9. Shell Programming and Scripting
Hi All
I need to transfer a file from a UNIX server to a windows server.
I saw that it is possible to do this using scp command by looking at the forum listed below:
... (2 Replies)
Discussion started by: vx04
2 Replies
10. Shell Programming and Scripting
I have a script, which connecting to remote server and first checks, if the files are there by timestamp. If not I want the script exit without error. Below is a code
TARFILE=${NAME}.tar
TARGZFILE=${NAME}.tar.gz
ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;... (3 Replies)
Discussion started by: digioleg54
3 Replies
LEARN ABOUT DEBIAN
comprez
Z(1) General Commands Manual Z(1)
NAME
comprez - safely (un)tar and (de)feather files and directories
SYNOPSIS
comprez [ -t | -T ] [ -v | -V ] [ -l | -L ] [ -gz | -z | -I | -lz | -Z | -zip | -jar ] [ -# ] [ -s suffix ] [ -m mode ] [ -p | -P ] [ -h ]
[ -- ] file ...
DESCRIPTION
Comprez is a simple, safe and convenient front-end for the compress(1), uncompress(1), gzip(1), bzip2(1), lzip(1), tar(1), zip(1) and
unzip(1) utilities for compressing and uncompressing files and directories. It processes each of its arguments according to the type of
the file or directory given:
If the argument is a plain file, then the file is compressed, ie, feathered.
If the argument is a compressed file with a name ending in .Z, .gz, .z, .bz2, .lz, .zip or .jar, then the file is uncompressed, ie,
defeathered.
If the argument is a directory, then the directory is archived into one tar or zip file which is then compressed, ie, tarred and feathered.
If the argument is a compressed tar or zip archive with a name ending in .{tar.,tar,ta,t}{Z,gz,z,bz2,lz} or .{zip,jar}, then the archive is
uncompressed and untarred, ie, untarred and defeathered.
The new compressed or uncompressed version will be in the same directory as the original. A compressed file is always uncompressed into a
file with the same name sans the feather suffix. A compressed tar or zip archive is always unpacked into a subdirectory with the same name
as the archive sans the tar and feather suffix, even if the archive did not itself contain such a subdirectory.
OPTIONS
-- Interprets all following arguments as files instead of options.
-# Where # is a digit from 1 through 9. This option is passed on to gzip(1), bzip2(1), lzip(1) and zip(1) when feathering with
them. --fast may be used instead of -1 and --best instead of -9.
-gz Uses gzip(1) and a .gz compression suffix when feathering.
-h Prints a helpful usage message.
-I Uses bzip2(1) and a .bz2 compression suffix when feathering.
-l Lists the file or directory name created resulting from each argument.
-L Does not report created files or directories. Default.
-lz Uses lzip(1) and a .lz compression suffix when feathering.
-m mode Apply the given chmod(1) mode argument to any created tar and feather files. Before this argument is applied, the files have the
same read and write permissions as the directories from which they were created. For security, the default argument is go-rwx.
If the mode is -, then no argument is applied. See chmod(1) for all other allowable formats of this argument.
-p Preserves modes when untarring by giving the p flag to tar(1). Default.
-P Doesn't preserve modes when untarring by not giving the p flag to tar(1). This option may be necessary on systems where ordinary
users are allowed to run chown(2).
-s suffix Creates tar and feather files using the given suffix style. The default suffix style is .tar.Z. Note that the suffix style does
not dictate the program used for feathering nor the compression suffix.
-t Only lists the table of contents of the given files. Does not make any changes.
-T (Un)tars and (de)feathers the given files according to their type. Default.
-v Verbose output. For example, reports compression ratios when feathering.
-V Non-verbose output. Does not report compression ratios. Default. -q is a synonym.
-z Uses gzip(1) and a .z compression suffix when feathering.
-Z Uses compress(1) and a .Z compression suffix when feathering. Default.
-zip, -jar
Uses zip(1) and a .zip or .jar compression suffix when tarring and/or feathering. The zip format combines tarring and feather-
ing. WARNING: zip does not preserve complete Unix filesystem information for the files it archives, such as links, some permis-
sions, etc. A tar(1)-based format should be used if this is required.
ENVIRONMENT VARIABLES
ZOPTS This variable may be set to a string of the above options to supersede the default settings. They may still be overridden by
options given on the command line.
GZIP This environment variable for gzip(1) is not passed on by comprez so that gzip's behavior is standard and predictable.
ZIPOPT, UNZIP
These environment variables for zip(1) and unzip(1) are not passed on by comprez so that their behavior is standard and pre-
dictable.
BUGS
There should be an option to allow the use of another directory for temporary files needed during the (un)tarring and (de)feathering pro-
cesses. This would make comprez more useful when the quota or disk is nearly full.
There should be -k and -K options for keeping the original input files or not.
CAVEATS
Comprez is written to work with gzip versions 1.2.3 and 1.2.4, bzip2 versions 0.9.0 and 1.0.0, Unix zip version 2.0.1 and Unix unzip ver-
sion 5.12. Other versions will probably work safely, too, but should still be checked for compatibility.
Every effort has been made to assure that the use of this program will not lead to the inappropriate deletion or corruption of any files.
However, there are never any guarantees, so please use at your own risk.
VERSION
2.6.1
AUTHOR
Steve Kinzler, kinzler@cs.indiana.edu, May 89/Jun 93/Aug 99/Dec 00
URL
http://www.cs.indiana.edu/~kinzler/z
SEE ALSO
compress(1), uncompress(1), gzip(1), bzip2(1), lzip(1), tar(1), zip(1), unzip(1)
2.6.1 Z(1)