Re: rsync 3.2.7 hangs when --usermap is used and receiver is not a super-user

2023-03-09 Thread Tomasz Chmielewski via rsync

On 2023-03-09 09:10, Tomasz Chmielewski via rsync wrote:

So from the tests above, it hangs with rsync 3.2.3 on the sender and 
rsync 3.2.7 on the receiver. I'll run some more tests.


Self-compiled rsync 3.2.7 on Debian to Ubuntu (rsync 3.2.7) - does NOT 
hang.



Tomasz Chmielewski

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: rsync 3.2.7 hangs when --usermap is used and receiver is not a super-user

2023-03-09 Thread Tomasz Chmielewski via rsync

On 2023-03-09 08:15, francis.montag...@inria.fr wrote:

Hi.

On Wed, 08 Mar 2023 22:21:28 +0100 Tomasz Chmielewski via rsync wrote:


After upgrading to rsync 3.2.7, the following command hangs forever
(using "--usermap" causes the hang; without "--usermap" it doesn't
hang):



rsync -v -p -e --usermap user:user /etc/services user@remote:


This command is incorrect: the -e option needs a command.

Without -e this command works for me on Fedora-37 with
rsync-3.2.7-1.fc37.x86_64


I've removed some excessive parameters and filenames from my original 
ones, but left over the "-e" which is indeed not needed there.


There seems to be some other requirements for it to be reproduced:

1) transfer on the localhost, Ubuntu 22.10 (rsync 
3.2.7-0ubuntu0.22.10.1) - NOT reproducible:


$ rsync -v -p --usermap tch:tch /etc/services tch@localhost:/tmp
services

sent 160 bytes  received 149 bytes  618.00 bytes/sec
total size is 12,813  speedup is 41.47
$


2) transfer from Debian 11 (rsync 3.2.3-4+deb11u1) to Ubuntu 22.10 
(rsync 3.2.7-0ubuntu0.22.10.1) - reproducible, hangs:


# rsync -p --usermap user:user /etc/services user@10.42.0.47:/tmp
[...never returns, needs ctrl+C...]

Also hangs when the user provided to --usermap does not exist

# rsync -p --usermap does-not-exist:does-not-exist /etc/services 
tch@10.42.0.47:/tmp

Unknown --usermap name on receiver: does-not-exist
[...never returns, needs ctrl+C...]


3) transfer from 22.10 (rsync 3.2.7-0ubuntu0.22.10.1) to Ubuntu 22.04 
(rsync 3.2.7-0ubuntu0.22.04.2) - NOT reproducible:


$ rsync -p --usermap does-not-exist:does-not-exist /etc/services 
tch@192.168.1.23:/tmp

Unknown --usermap name on receiver: does-not-exist
$


4) transfer from Debian 11 (rsync 3.2.3-4+deb11u1) to Ubuntu 22.04 
(rsync 3.2.7-0ubuntu0.22.04.2) - reproducible, hangs:


# rsync -p --usermap does-not-exist:does-not-exist /etc/services 
tch@192.168.1.23:/tmp

Unknown --usermap name on receiver: does-not-exist
[...never returns, needs ctrl+C...]



So from the tests above, it hangs with rsync 3.2.3 on the sender and 
rsync 3.2.7 on the receiver. I'll run some more tests.



Tomasz Chmielewski

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: rsync 3.2.7 hangs when --usermap is used and receiver is not a super-user

2023-03-08 Thread Francis.Montagnac--- via rsync


Hi.

On Wed, 08 Mar 2023 22:21:28 +0100 Tomasz Chmielewski via rsync wrote:

> After upgrading to rsync 3.2.7, the following command hangs forever 
> (using "--usermap" causes the hang; without "--usermap" it doesn't 
> hang):

> rsync -v -p -e --usermap user:user /etc/services user@remote:

This command is incorrect: the -e option needs a command.

Without -e this command works for me on Fedora-37 with
rsync-3.2.7-1.fc37.x86_64

-- 
francis

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


rsync 3.2.7 hangs when --usermap is used and receiver is not a super-user

2023-03-08 Thread Tomasz Chmielewski via rsync
After upgrading to rsync 3.2.7, the following command hangs forever 
(using "--usermap" causes the hang; without "--usermap" it doesn't 
hang):


rsync -v -p -e --usermap user:user /etc/services user@remote:

It did not hang with rsync 3.2.3.

Not sure if it's intended behaviour? The fine manual says that --usermap 
should be used as a super-user on the receiver, but does not mention 
that it will hang if used as a non-super-user.


Reproducible on Ubuntu 20.04 LTS.


Tomasz Chmielewski

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html