JT> When I tar up a directory on a solaris box and then ftp JT> (push) from the solaris box to a RH8.0 box (solaris box is JT> the ftp client, RH8.0 box is the ftp server), the subsequent JT> untar operation on the RH8.0 box fails with:
JT> # tar -xf myfile.tar JT> tar: Skipping to next header JT> tar: Skipping to next header JT> tar: Error exit delayed from previous errors
JT> However, if I get that same tar by ftp (pull) from solaris box JT> to RH8.0 box (RH8.0 is ftp client, solaris box is ftp server), JT> the untar works fine.
JT> Any ideas?
Are you making sure to set the mode to binary in the first instance?
_________________________________________________________________ Brian Ashe CTO [EMAIL PROTECTED] Dee-Web Software Services, LLC. http://www.dee-web.com/ -----------------------------------------------------------------
Brian...so that was insightful...switching to binary worked...I'm open to learning something new. Over the years I have evolved to being very specific about controlling ascii/binary mode in ftp based on content. This has been especially necessary with the whole dos2unix thing when ftp'ing between Windoz and Unix.
The directory I was trying to ftp contained only flat ascii text files. The last time I checked, tar will create a flat ascii text tile if all the files being tarred are ascii. Therefore, when I ftp, I make sure that that I am in ascii mode (old habits...know what you're ftp'ing and get the right mode).
Yet that was the problem. When ftp'ed as ascii, the untar failed. But when ftp'ed as binary the untar succeeded. This was the case when the ftp server was on the RedHat side (and I "pushed" to the linux box).
But, when I "pulled" to the linux, with the ftp server on the Solaris side, it did not matter when I used binary or ascii...both untars worked.
This is what I would expect with a true ascii file...you can ftp in either mode and it will work. In other words, my experience has been that if I have an ascii file, I can use either binary or ascii to ftp it and it will work (except that binary mode will plant unwanted ^m's at the end of every line). But if I have a binary file, I must transfer in binary mode only.
So...any ideas why RH8.0 ftp server is behaving differently than Solaris ftp server?
Jay
----------------------------------------------------------------------- Jay Thompson Support Systems Analyst, Sr. Northern Arizona University College of Ecosystem Science and Management [EMAIL PROTECTED] (520) 523-8033
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
