On Tue, Feb 7, 2012 at 5:22 AM, Michael Simpson wrote:
>
>> https://bugzilla.redhat.com/show_bug.cgi?id=724041
>>
>> which was fixed nearly a month ago.
>
> So instead of saying nearly a month ago how about we we say it was only
> released 20 days ago. BZ says it was released 03 Aug 11.
>
>>
>> If
On 31 January 2012 22:14, Les Mikesell wrote:
> On Tue, Jan 31, 2012 at 4:01 PM, wrote:
>>> On Tue, Jan 31, 2012 at 3:14 PM, Ljubomir Ljubojevic
>>> wrote:
On 01/31/2012 09:47 PM, Les Mikesell wrote:
> No, I'm trying to have rsync make an outbound connection over ssh from
> the res
On Tue, Jan 31, 2012 at 4:01 PM, wrote:
>> On Tue, Jan 31, 2012 at 3:14 PM, Ljubomir Ljubojevic
>> wrote:
>>> On 01/31/2012 09:47 PM, Les Mikesell wrote:
No, I'm trying to have rsync make an outbound connection over ssh from
the rescue environment and getting what looks like an argumen
On 01/31/2012 10:58 PM, Les Mikesell wrote:
> On Tue, Jan 31, 2012 at 3:14 PM, Ljubomir Ljubojevic wrote:
>> On 01/31/2012 09:47 PM, Les Mikesell wrote:
>>> No, I'm trying to have rsync make an outbound connection over ssh from
>>> the rescue environment and getting what looks like an argument err
On Tue, Jan 31, 2012 at 3:14 PM, Ljubomir Ljubojevic wrote:
> On 01/31/2012 09:47 PM, Les Mikesell wrote:
>> No, I'm trying to have rsync make an outbound connection over ssh from
>> the rescue environment and getting what looks like an argument error
>> from ssh. Ssh itself works and I can conn
On 01/31/2012 09:47 PM, Les Mikesell wrote:
> No, I'm trying to have rsync make an outbound connection over ssh from
> the rescue environment and getting what looks like an argument error
> from ssh. Ssh itself works and I can connect to the same target if I
> run it directly, and the exact same
On Tue, Jan 31, 2012 at 1:50 PM, wrote:
>
>>> That's odd, try rsync -e 'ssh -v' to get some more details.
>>> Also you will want to use some parameters to rsync (like -av or maybe
>>> even
>>> -z for compression etc).
>>
>> I'm getting a
>> usage: ssh [bunch of ssh options]
>> like it is giving
On Tue, Jan 31, 2012 at 1:07 PM, wrote:
>>>
>>> What commands are you using exactly? To or from the rescued host? Also, are
>>> you using ssh non-standard ports?
>>
>> It is from the rescued host - basically a:
>> rsync -essh otherhost:/path .
>>
>> ssh otherhost 'cd /path && tar -cf - ' | tar -
Les Mikesell writes:
> On Tue, Jan 31, 2012 at 12:29 PM, wrote:
>> Les Mikesell writes:
>>
>>> If I boot a 5.7 install disk with 'linux rescue selinux=0', let it
>>> start the network and detect the installed system, ssh seems to work,
>>> but rsync fails with "rsync: connection unexpectedly cl
On Tue, Jan 31, 2012 at 12:29 PM, wrote:
> Les Mikesell writes:
>
>> If I boot a 5.7 install disk with 'linux rescue selinux=0', let it
>> start the network and detect the installed system, ssh seems to work,
>> but rsync fails with "rsync: connection unexpectedly closed (0 bytes
>> received so
Les Mikesell writes:
> If I boot a 5.7 install disk with 'linux rescue selinux=0', let it
> start the network and detect the installed system, ssh seems to work,
> but rsync fails with "rsync: connection unexpectedly closed (0 bytes
> received so far) [receiver]). Shouldn't it work as long as t
If I boot a 5.7 install disk with 'linux rescue selinux=0', let it
start the network and detect the installed system, ssh seems to work,
but rsync fails with "rsync: connection unexpectedly closed (0 bytes
received so far) [receiver]). Shouldn't it work as long as the
underlying ssh connection w
12 matches
Mail list logo
