I have done a number of installs, and it pretty much always seems that the tar has an ignore-worthy error. Regardless, it would be really kind if in "Code listing 19" the tar command read: # tar -xvjpf /path/to/stage?-*.tbz2 &> unTarStage.out & # tail -f unTarStage.out of something to that affect
think about it further maybe best just to redirect std err
How is this a bug. If tar pukes at the end of the untaring process, won't it be visible at the bottom of the std output? I mean, this is what tail does anyway. //ZhEN
There are many errors where 'tar' will not "puke", but "suppress" the failure till completion of the tar command. If you do not pipe to a file then you have to reissue the tar command and direct the output to a file -- which is wasteful. I am not sure what the reference to 'tail' in the last comment is suggesting. I will leave it to "your" discression whether to reopen or not.
ZhEN: what we was suggesting was to help out newbies ... basically, when you run that tar command and extract the contents of the file, there are usually a few warnings/errors that can be safely ignored. people who are used to this kind of stuff just ignore them, but newbies maybe be confused with it ... although i think this would be cool to have, those few times where the extraction didnt work, the newbie wouldnt know what to do or how to check for errors or any of that ... in other words, i say this is well intentioned but may cause some problems for some people
I agree. I think that this is one of those things that could potentially cause more problems than it would fix. I am leaving this closed. //ZhEN
