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