works fine, has 63 characters in the remote tarfilepath. Add one more:
address@hidden leaver]$ tar -cvf ssslnxm:/home/leaver/tartest/file67890123456789012345678901234567890.tar tmp
tar: ssslnxm\:/home/leaver/tartest/file67890123456789012345678901234567890.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
address@hidden leaver]$ echo $?
2
works not so fine. In this case I'm working pseudo-remote, but it makes (little) difference.
Here's 62 characters.
address@hidden leaver]$ tar -cvf node10:/home/leaver/tartest/file678901234567890123456789012345678.tar tmp; echo $?
tmp/
tmp/foo
0
Add one more character:
address@hidden leaver]$ tar -cvf node10:/home/leaver/tartest/file6789012345678901234567890123456789.tar tmp; echo $?
tar: node10\:/home/leaver/tartest/file6789012345678901234567890123456789.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
2
These above tars were version 1.13.25 on Red Hat 7.3. Switch to 1.15.1 and gain a modicum of consistency:
Thats 63 characters: Still fails at 64:
address@hidden leaver]$ /opt/osi-ir/bin/tar -cvf node10:/home/leaver/tartest/file67890123456789012345678901234567890.tar tmp; echo $?
/opt/osi-ir/bin/tar: node10\:/home/leaver/tartest/file67890123456789012345678901234567890.tar: Cannot open: No such file or directory
/opt/osi-ir/bin/tar: Error is not recoverable: exiting now
2
Fine, Red Hat 7.3 is dead. Switch to node10, which is CentOS-4.2 and GnuTar version 1.14:
62 characters:
address@hidden leaver]$ tar -cvf node10:/home/leaver/tartest/file678901234567890123456789012345678.tar tmp; echo $?
tmp/
tmp/foo
0
63 characters:
address@hidden leaver]$ tar -cvf node10:/home/leaver/tartest/file6789012345678901234567890123456789.tar tmp; echo $?
tmp/
tmp/foo
tar: node10:/home/leaver/tartest/file6789012345678901234567890123456789.tar: Wrote only 4089 of 10240 bytes
tar: Error is not recoverable: exiting now
2
Facinating, Captain... But 64 characters still fails completely:
address@hidden leaver]$ tar -cvf node10:/home/leaver/tartest/file67890123456789012345678901234567890.tar tmp; echo $?
tar: node10\:/home/leaver/tartest/file67890123456789012345678901234567890.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
2
Try GnuTar 1.15.1 with 63 characters and 64:
address@hidden leaver]$ /opt/osi-ir/bin/tar -cvf node10:/home/leaver/tartest/file6789012345678901234567890123456789.tar tmp; echo $?
tmp/
tmp/foo
0
address@hidden leaver]$ /opt/osi-ir/bin/tar -cvf node10:/home/leaver/tartest/file67890123456789012345678901234567890.tar tmp; echo $?
/opt/osi-ir/bin/tar: node10\:/home/leaver/tartest/file67890123456789012345678901234567890.tar: Cannot open: No such file or directory
/opt/osi-ir/bin/tar: Error is not recoverable: exiting now
2
...........................................................................................................
GnuTar 1.13.25 behaves the same on Fedora Core 2 as on Red Hat 7.3. My GnuTar 1.15.1 was compiled on the Red Hat 7.3 system using gcc-3.3.6, all config flags default except for --prefix. (The CentOS systems have 7.3 compatibility libraries installed. My FC2 system apparently does not.)
I do not see any such tarfilepath length limitation on local tarfiles, beyond (or should I say, before) the usual PATH_MAX.
So, before I dig any further, is this remote tarfilepath length limitation a feature, or a bug?
Or is it something else I haven't even thought of yet? Any ideas? Suggestions?