On Sun, Sep 18, 2022 at 6:13 AM Paul Slootman wrote:
> IMHO rsync is correct in refusing to run with a missing rsyncd.conf.
>
Yeah, it's one of the ways that some installs prevent a superfluous daemon
from starting up -- if it's not configured, you don't want it.
..wayne..
--
Please use
On Tue, Sep 20, 2022 at 11:21 AM İhsan Doğan via rsync <
rsync@lists.samba.org> wrote:
> ./mkgitver
> ./mkgitver: test: argument expected
>
Looks like your OS's "test" doesn't support "-e". If you tweak the "if [
-e" to be "if [ -d" you should be fine.
..wayne..
--
Please use reply-all for
Hi,
While rsync 3.2.5 was building fine on Solaris 10, I’m running into this error
with 3.2.6:
/opt/SUNWspro/bin/cc -I. -I. -I./zlib -xO3 -m32 -xarch=sparc -DHAVE_CONFIG_H
-I/opt/csw/include -c uidlist.c -o uidlist.o
/opt/SUNWspro/bin/cc -I. -I. -I./zlib -xO3 -m32 -xarch=sparc -DHAVE_CONFIG_H
Indeed, we have “use chroot = false” – our application is a file distribution
system where users authenticate as themselves and run rsync daemonized over ssh
transport, rrsync-style. We can’t run with “use chroot = true” as a workaround
since the users are not root, and the chroot() system
The branch, master has been updated
via 97e02bf2 Some "use chroot" improvements.
via 77d762ce Stop importing "re".
from 5b27d2e6 Pre-compute FILE_SUM_EXTRA_CNT.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
