similar to: handling of 'use chroot'

I just took a look at the 2.5.5 codebase to see how easy it would be to write a little driver script that downloads a big directory tree from an rsync daemon the chunky way (get a list of a module's subdirectories and do the transfer by subdirectory). The reason for doing this is obvious when you have large directory trees, as is the case for many of us. Unfortunately the way list_only is

Dear all, I've been trying to track down a problem with timeouts when pulling data from an rsync daemon and I have now run out of any useful ideas. The problem manifests itself when I try to transfer a large directory tree on a slow client machine. What happens then is that the client rsync process successfully receives the list of files from the server, then begins checking the local

Is there a good place to get information about the list of all possible output and error messages rsync generates? Or should I just muck around the source code (which I haven't looked at yet) and find them? I am doing something where I would like to parse rsync's output using Perl into a set of data structures. I already have something that works under normal conditions. Eventually

I was at first, but then removed it. The results were still insufficiently fast. > Were you using the -c option of rsync? It sounds like you > were and it's > extremely slow. I knew somebody who once went to > extraordinary lengths to > avoid the overhead of -c, making a big patch to rsync to > cache checksums, > when all he had to do was not use -c.

Hi, I am thinking about a non-standard usage of rsync (at least not mentioned in the man file) I want to synchronized my collegues home directories(trees) each night AND store rsync's internal updating commands (reversed) to be able to restore the state of a directory the day before. This would require - saving the internal updating commands in a separate directory - reversing these commands

Le Jeudi 11 Avril 2002 21:09, m.ibarra at cdcixis-na.com a ?crit : > I was curious to know if you had any luck in getting openssh's sftp > server properly configured to allow chrooted sftp logins? I have had > no success and need something quickly. Dear Mike, Unfortunately, I did not succeed to have it work. I got in contact with James Dennis <jdennis at law.harvard.edu>, who

Hi all, Tripped over a documentation bug. I'm guessing the behavior I've found isn't a bug in itself as it's kind of implied by chroot (unless the /etc/passwd db is read *before* you do the chroot call), so I'm calling it a documentation bug. The Setup: System A: running rsync --daemon from xinetd, configured with a read-only share. System B: syncing a local directory

Hello, I am trying to run rsync under my own userid on a high-numbered port. The problem is that, when I use the --daemon option, I get an error saying that a chroot() call failed. My config file does *not* have any chroot call in it. How can I avoid a chroot() invocation when running as a normal non-root user? Thanks in advance for any advice! -- Daniel Ortmann, LSI Logic, 3425 40th Av NW,

Rsync list: Alberto and I have done a couple more exchanges by private email, and we found that he wasn't turning on my include/exclude optimization in his test because he had an "exclude" directive in rsyncd.conf. He has now removed that and run the test again. His very interesting results are below with my comments. Note that his case is rather pathological because he's got

I am using rsync 2.5.5 running as a daemon on the destination system, which is SuSE Linux 8.0. The source system is SuSE 7.3, also with rsync 2.5.5. With the default 'use chroot = true' and not using --numeric-ids, I get the wrong user names on the destination files. I have tracked this down to getpwnam() failing to return the user name from the passwd file. It does not fail when

https://bugzilla.samba.org/show_bug.cgi?id=11013 Bug ID: 11013 Summary: [patch] Mention that privileges are dropped, when "use chroot" is enabled in rsyncd.conf manpage Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5

Hi All, I'm migrating a CentOS 6 bind instance (chrooted) to a CentOS 7 box and am curious of people's opinions on chrooting vs selinux as a way of securing bind. The bind-chroot on CentOS 7 also comes with a script (/usr/libexec/setup-named-chroot.sh) that sets up the much maligned systemd and, through bind mounts, creates and extra level of chroot hierarchy giving:

Hi Everybody, I'm new to this list, but I have been using rsync for quite some time. First, congratulations to the rsync team for a very fine piece of software! I'm wondering whether rsync could help me to perform the following task: I have 5 million files on one side of the ocean, 100000 of which must be copied to the other side. Both numbers grow with time, and occasionally, some

The subject says it all :-) Apparently in pre-3.0.0 versions '%P' would log the actual path as specified in the module entry in rsyncd.conf, but now it's apparently relative to the chroot... Paul Slootman

Took a while to figure this one out: Since "use chroot" defaults to true, I was having issues of UID/GID's not mapping between servers. On AIX, if chroot() is called, the getpwuid() calls fail, no longer being able to find /etc/passwd. Since the that call doesn't differentiate between a 'failure' and a 'unable to map uid', rsync assumes it can't map the

https://bugzilla.samba.org/show_bug.cgi?id=12817 Bug ID: 12817 Summary: [PATCH] Allow daemon itself to chroot Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Hi, I'm running rsyncd in daemon mode started via xinetd. My /etc/rsyncd.conf looks like: [cache] path = /mnt/tst_vol_aws/sat_p_cache/ comment = Cache Directory use chroot = false read only = false uid = someone gid = someone dont compress = * On the client I run: /usr/bin/rsync --delete --ignore-errors -gpzsoltD --temp-dir=/mnt/tst_vol_aws/tmp/rsync -r

Hello, evevryone. thank you for your mails. I used rsync(rsync-2.4.6-2) for backup Server.(My Linux is RedHat7.1) I am very comfortable backup system by rsync. but, I saw this messages in use rsyncd daemon.(/var/log/messages) I don't know mean this messages. but, It is right use rsyncd. and I used rsyncd at every day. but this messages writed log at every minute(?) or every time. What

Hi. While debugging some encfs errors in the logs, I realized they are being generated because rsync (chrooted inside a encfs file system, --reverse) is trying to access files like: /root/.popt, /etc/localtime etc. This doesn't seem to be related to ID-name mapping as I already have numeric ids enabled in config. Here is the relevant strace output: [pid 25549] chroot("/chroot")

Hi, I am not sure it this still is a point, but I just discovered that a chrooted rsync version 2.6.3pre1 is forgetting the time zone underways: Jan 12 07:00:01 ftp4 rsyncd[11091]: rsync on dobes/ from dobes@edoc1.gwdg.de (134.76.28.251) Jan 12 06:00:39 ftp4 rsyncd[11091]: wrote 732542 bytes read 182 bytes total size 553909487945 Logging is done with syslog. Time zone is GMT+1, the system