>Use it anyways, no one has ever accused you of being a human -=]
>
>Patrick
[ahem!] Yes, well, on that note, I offer my wishes to the sentient
beings on this channel (and also to Patrick) that this season
brings you all the happiness you might prudently wish for... ;->
_
> Having just now quickly RTFSC and done a few superficial experiments I
> conclude that the -t option (mnemonic for "to"; there's also a secret "from"
> flag -f) is not suitable for use by humans. It tells scp that it's in
> "server"
> mode and should expect to communicate with its counterpart u
Having just now quickly RTFSC and done a few superficial
experiments I conclude that the -t option (mnemonic for "to";
there's also a secret "from" flag -f) is not suitable for
use by humans. It tells scp that it's in "server" mode and
should expect to communicate with its counterpart using some
That's typical of the workarounds suggested by those who thought that
scp was unable to read from stdin. My question was really about why
the functionality is undocumented, since scp actually *is* able to
read from stdin,
On Thu, Dec 22, 2011 at 4:33 PM, Thomas Charron wrote:
> Not sure about
On Thu, Dec 22, 2011 at 4:35 PM, Shawn O'Shea wrote:
>
> dd if=infile | ssh remotehost dd of=outfile
> or
> tar cf - | ssh remotehost tar xvf -
>
>
Oops, forgot the infile in my 2nd example. Should be:
tar cf - infile | ssh remotehost tar xvf -
-Shawn
On Thu, Dec 22, 2011 at 4:25 PM, John Abreau wrote:
> Long ago, I was looking for a way to make scp read from stdin, and I
> had no luck.
>
Is this documented anywhere? I don't understand why the option would be
> left out of the man page.
>
>
Although I've never heard of the -t option to scp m
Not sure about scp, but you could use:
ssh 192.168.1.2 "cat > destFile"
On Thu, Dec 22, 2011 at 4:25 PM, John Abreau wrote:
> Long ago, I was looking for a way to make scp read from stdin, and I
> had no luck.
>
> Earlier this afternoon, when I was tweaking my "validate-rsync" script to add
> su
Long ago, I was looking for a way to make scp read from stdin, and I
had no luck.
Earlier this afternoon, when I was tweaking my "validate-rsync" script to add
support for scp, I discovered that when running the command
> scp foo remote:/path/to/bar
the remote end gets invoked as
> scp -t /pat
