Stuart Howard wrote:
Yes I am using samba to connect to the XP box as you suggested.
The error report arrived via mail from a cron, prehaps the garbling of
the message occured there?
Anyway thanks again for responses, I usually clean up /tmp after the
script runs so I made the assumption later on that the error was at
the point of creation of the file and not during the cp, so as a way
of confirming this I have set it off again to make the very large tgz
and then try too cp it via samba transport to the XP box. [will run
overnight now]
If it works ie. if the full file is created [waiting in /tmp] then it
is samba or if not then a post back to the shell limit. Should know by
morning.
An interesting chase regardless and if it is samba then will have to
split the tgz.
Mounting it as a "smbfs" filesystem (which does not support file larger
than 2G) is almost certainly the problem. Try mounting the XP box as a
"cifs" (mount.cifs) filesystem and you should have better luck.
-Richard
--
[email protected] mailing list
