On Wed, 14 Apr 2021, Leon Fauster via CentOS wrote:
On 14.04.21 06:40, Frank Cox wrote:
This doesn't work:
Host *
ForwardX11 yes
host jeff
ForwardX11 no
IMHO - first win. It should be
Host jeff
ForwardX11 no
Host *
ForwardX11 yes
I think that's right. My ssh config has what amounts to
On 14.04.21 06:40, Frank Cox wrote:
This doesn't work:
Host *
ForwardX11 yes
host jeff
ForwardX11 no
IMHO - first win. It should be
Host jeff
ForwardX11 no
Host *
ForwardX11 yes
--
Leon
___
CentOS mailing list
CentOS@centos.org
On Tue, 13 Apr 2021 23:36:48 -0400
Chris Schanzle via CentOS wrote:
> I discovered if I set ForwardX11=no (either on ssh command line or in
> ~/.ssh/config) the hang does not happen. But why does that matter? No
> updates to openssh.
Far out! That's the solution!
Well, not really a solution
On 4/13/21 5:00 PM, Frank Cox wrote:
> On Tue, 13 Apr 2021 22:29:26 +0200
> Simon Matter wrote:
>
>> You could try running strace on the hanging process so see what it's doing.
> [frankcox@mutt temp]$ rsync -avv ../temp/ jeff:temp
> opening connection using: ssh jeff rsync --server
On Tue, 13 Apr 2021 22:29:26 +0200
Simon Matter wrote:
> You could try running strace on the hanging process so see what it's doing.
[frankcox@mutt temp]$ rsync -avv ../temp/ jeff:temp
opening connection using: ssh jeff rsync --server -vvlogDtpre.iLsfxC . temp (7
args)
sending incremental file
> On Tue, 13 Apr 2021 12:09:42 -0700 (PDT)
> Paul Heinlein wrote:
>
>> Is there any chance that your shell is configured to emit anything to
>> stderr or stdout when you logout of jeff? It's fairly rare, but I've
>> seen logout messages mess up rsync before.
>
> I don't think so. The only change
On Tue, 13 Apr 2021 12:09:42 -0700 (PDT)
Paul Heinlein wrote:
> Is there any chance that your shell is configured to emit anything to
> stderr or stdout when you logout of jeff? It's fairly rare, but I've
> seen logout messages mess up rsync before.
I don't think so. The only change from the
On Tue, 13 Apr 2021, Frank Cox wrote:
Here's a weird one.
I have two Centos 8 machines that use rsync-over-ssh to back up files between
each other. (Each machine acts as a backup machine for the other one.)
There's are nightly cronjobs that do the backing up, the commands look like
this:
On Tue, 13 Apr 2021 13:07:19 -0500
Christopher Wensink wrote:
> Try using --whole-file / -W
Using that command, it says "delta-transmission disabled for local transfer or
--whole-file
", but it still stalls at the end so there's no change.
Since it works fine transferring files over nfs, it
Try using --whole-file / -W
On 4/13/2021 12:52 PM, Frank Cox wrote:
On Tue, 13 Apr 2021 12:43:16 -0500
Christopher Wensink wrote:
Does it behave any differently when adding a & at the end of the command
when running it manually, or running in a screen session?
Nope. I get the same stall
On Tue, 13 Apr 2021 12:43:16 -0500
Christopher Wensink wrote:
> Does it behave any differently when adding a & at the end of the command
> when running it manually, or running in a screen session?
Nope. I get the same stall both ways. Running it in a screen session looks
exactly like what I
Does it behave any differently when adding a & at the end of the command
when running it manually, or running in a screen session?
Chris
On 4/13/2021 11:45 AM, Frank Cox wrote:
Here's a weird one.
I have two Centos 8 machines that use rsync-over-ssh to back up files between
each other.
Here's a weird one.
I have two Centos 8 machines that use rsync-over-ssh to back up files between
each other. (Each machine acts as a backup machine for the other one.)
There's are nightly cronjobs that do the backing up, the commands look like
this:
rsync -av --delete /home/mydirectory
13 matches
Mail list logo
