Copied files take up more space than originals
in [Solaris]
|
Prev: Value too large for defined data type...
Next: Problem when multiple SCP connections in Solaris 10 - ssh_exchange_identification: Connection closed by remote host
From: Nico Kadel-Garcia on 22 Dec 2009 18:22 On Dec 22, 4:24 pm, Dave <f...(a)coo.com> wrote: > Is there any way to get scp to not do this? No. SCP is based on the behavior of a *much* older tool called 'rcp', and 'rcp' was never sophisticated enough to handle symlinks as symlinks rather than as binary files. I've not explored whether sftp can do this properly. But in general, if you want efficient transmission of symlinks and/or hardlinks, use rsync or rsync over SSH.
From: unruh on 23 Dec 2009 00:22 ["Followup-To:" header set to comp.security.ssh.] On 2009-12-23, Dave <foo(a)coo.com> wrote: > Nico Kadel-Garcia wrote: >> On Dec 22, 4:24 pm, Dave <f...(a)coo.com> wrote: >> >>> Is there any way to get scp to not do this? >> >> No. SCP is based on the behavior of a *much* older tool called 'rcp', >> and 'rcp' was never sophisticated enough to handle symlinks as >> symlinks rather than as binary files. > > On might hope that the developers would look at improving matters in this > respect, with an option which allows links to be copied properly. Why? There are many better file copy commands ( like rsync). Why reinvent the wheel yet again. What is it about scp that you feel that you cannot use something else? scp is useful sometimes. Other times it is not. Do not use it when it is not useful. > >> I've not explored whether sftp can do this properly. But in general, >> if you want efficient transmission of symlinks and/or hardlinks, use >> rsync or rsync over SSH. > > Thank you.
From: Dave on 22 Dec 2009 20:21 Nico Kadel-Garcia wrote: > On Dec 22, 4:24 pm, Dave <f...(a)coo.com> wrote: > >> Is there any way to get scp to not do this? > > No. SCP is based on the behavior of a *much* older tool called 'rcp', > and 'rcp' was never sophisticated enough to handle symlinks as > symlinks rather than as binary files. On might hope that the developers would look at improving matters in this respect, with an option which allows links to be copied properly. > I've not explored whether sftp can do this properly. But in general, > if you want efficient transmission of symlinks and/or hardlinks, use > rsync or rsync over SSH. Thank you. -- I respectfully request that this message is not archived by companies as unscrupulous as 'Experts Exchange' . In case you are unaware, 'Experts Exchange' take questions posted on the web and try to find idiots stupid enough to pay for the answers, which were posted freely by others. They are leeches.
From: hume.spamfilter on 22 Dec 2009 21:02 In comp.unix.solaris Dave <foo(a)coo.com> wrote: > drkirkby(a)kestrel:~$ scp -pr sage-4.2 sage(a)t2nb: As others have mentioned, scp doesn't act like an archiver, figuring out what kind of file it is. (It's somewhat logical, since the remote system might not have an equivalent file type...) I'd do the following myself: tar cf - sage-4.2 | ssh sage(a)t2nb tar xvf - -- Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: David Kirkby on 23 Dec 2009 21:00
On Dec 23, 3:21 pm, ChrisS <chris.sca...(a)gmail.com> wrote: > I would definitely use the tar solution or the rsync solution. Since > it's a relatively small amount of data 'tar' may be easiest. > > I live for rsync these days too. I'm not sure rsync comes with > Solaris 10 by default. I've added it via Blastwave or OpenCSW, but > SunFreeware tools is good for that too. > > Good luck. > > Chris Semi-related to this, I do need to find a way of copying files and preserving links, like the '-a' option does on GNU 'cp'. I think creating a tar archive and then extracting it might be one way, but I'd like to avoid the need to create an intermediate file if possible. Dave (PS, I am the original poster, also known as foo(a)coo.com depending on what computer I happen to use) |