Hi
I have a process that creates 'some data' and outputs this to standard
out and i want to shift this data over ssh to a remote box without
ever writing anything locally. I have been experimenting with tar to
create the archive as the i dont know what the contents of 'some data'
might be so i
Tom Brown wrote:
Hi
I have a process that creates 'some data' and outputs this to standard
out and i want to shift this data over ssh to a remote box without
ever writing anything locally. I have been experimenting with tar to
create the archive as the i dont know what the contents of 'some
On 08/12/2010 05:33 AM, Les Mikesell wrote:
Why do you need any other process involved to work with a data stream? If you
want to collect it to a remote file, you can | ssh remotehost 'cat
path_to_file'. Just be sure to quote the redirection so it happens on the
remote side.
At a
At Thu, 12 Aug 2010 13:11:21 +0100 CentOS mailing list centos@centos.org
wrote:
Hi
I have a process that creates 'some data' and outputs this to standard
out and i want to shift this data over ssh to a remote box without
ever writing anything locally. I have been experimenting with tar
At Thu, 12 Aug 2010 06:05:25 -0700 CentOS mailing list centos@centos.org
wrote:
On 08/12/2010 05:33 AM, Les Mikesell wrote:
Why do you need any other process involved to work with a data stream? If
you
want to collect it to a remote file, you can | ssh remotehost 'cat
Robert Heller wrote, On 08/12/2010 09:18 AM:
At Thu, 12 Aug 2010 06:05:25 -0700 CentOS mailing list centos@centos.org
wrote:
On 08/12/2010 05:33 AM, Les Mikesell wrote:
Why do you need any other process involved to work with a data stream? If
you
want to collect it to a remote file, you
On Thu, Aug 12, 2010 at 09:18:31AM -0400, Robert Heller wrote:
program | bzip2 | ssh -q remote-host 'bunzip2 | remote-program'
If you're gonna put a compression tool in the pipeline then I recommend
you ensure ssh's own on-the-wire compression is turned off 'cos otherwise
you're potentially
Why not just do
`the thing that generates standard out here` | ssh -q 192.168.122.2 dd
of=somethin
eg
find . | ssh -q 192.168.122.2 dd of=find.out
You don't need tar for anything.
alas the thing that generates the output creates 5 or 6 seperate
streams in sequence that generate 5 or
On 8/12/2010 8:46 AM, Tom Brown wrote:
Why not just do
`the thing that generates standard out here` | ssh -q 192.168.122.2 dd
of=somethin
eg
find . | ssh -q 192.168.122.2 dd of=find.out
You don't need tar for anything.
alas the thing that generates the output creates 5 or 6 seperate
At Thu, 12 Aug 2010 14:46:49 +0100 CentOS mailing list centos@centos.org
wrote:
Why not just do
`the thing that generates standard out here` | ssh -q 192.168.122.2 dd
of=somethin
eg
find . | ssh -q 192.168.122.2 dd of=find.out
You don't need tar for anything.
alas
Rsync works fine for this, keeping group and user
Regards
2010/8/12, Robert Heller hel...@deepsoft.com:
At Thu, 12 Aug 2010 14:46:49 +0100 CentOS mailing list centos@centos.org
wrote:
Why not just do
`the thing that generates standard out here` | ssh -q 192.168.122.2 dd
of=somethin
On 08/12/2010 06:46 AM, Tom Brown wrote:
alas the thing that generates the output creates 5 or 6 seperate
streams in sequence that generate 5 or 6 log files but i dont know in
advance the names of these logs.
If the thing is generating log files, then it's not using standard
out. Perhaps you
12 matches
Mail list logo
