similar to: Rsync 2.6.9pre2 tries to read ACLs of nonexistent files

As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been

Oops :) -- quote -- $ rsync -aHPv rsync://host/module/single.file . <motd, if any> receiving file list ... 1 file to consider Segmentation fault -- endquote -- The rsync process remains running until explicitly 'kill'ed. At which point, the following is printed: -- quote -- rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(225) -- endquote -- -- quote -- $ rsync -aHPv

I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes. It dumps core when preserve_hard_links and backup. And SUPPORT_HARD_LINKS is true. rsync -avH --delete --backup --backup-dir=/some/backup/dir \ srchost::dir/ dir/ The core says... ------------------------------------------------------------------------ Program terminated with signal 11, Segmentation fault. #0 0x80536c0 in keep_backup

The generator can skip a directory's contents altogether due to --ignore-non-existing, a daemon exclude, or a mkdir failure. On a --dry-run, the generator can also note the missingness of a directory while still scanning its contents. These two scenarios were conflated using a single set of missing_below/missing_dir variables in combination with transient increments in dry_run; this caused

Here's a patch that makes rsync try to find an existing file in a group of hard-linked files so that it doesn't create the first one in the group from scratch if a later file could be used instead. Details: I decided to avoid having the code do an extra scan down the list when we encounter the lead file in the list. This is because it would be bad to have to do the same scan in the

https://bugzilla.samba.org/show_bug.cgi?id=8665 Summary: Crash in free_xattr(), from recv_generator() Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au

Use the cleanup handlers to free the structs (and list of structs) in case their OCaml->C transformation fails for any reason; use calloc() to not try to use uninitialized memory. In case of lists, avoid allocating the memory for the array if there are no elements, since the returned pointer in that case is either NULL, or a free()-only pointer; also, set the list size only after the array is

I have usccessfully installed Samba-3.0.10 on a Sun workstation running Solaris 10. I am now trying to view the shared directory on a laptop running Windows XP Home. I am only using Samba for a workgroup share as I know XP Home can not log on to a domain. I can see the Samba server on the XP laptop when I selecet "view workgroup computers". However, when I try to select the Samba server

On January 15, 2018 1:53 AM, Wayne Davison write: >I have made rsync 3.1.3pre1 available for testing. This release has a couple security fixes, a few new features, and a smattering of bug fixes. >Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. Incompatibility introduced at 3.1.3pre1. These are not present at master, which

https://bugzilla.samba.org/show_bug.cgi?id=13224 Bug ID: 13224 Summary: New file handling causes compile issues for NonStop port. Product: rsync Version: 3.1.3 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: core Assignee:

On 3/2/07, Wayne Davison <wayned@samba.org> wrote: > Make the auto-generated protect filters use the perishable flag so > that they don't stop a vanished directory from being removed. 1. I don't think the --backup rule should be perishable. If I delete an entire directory from the source, I would expect the receiver to back up the files inside and not discard the backups just

This is just a basic ugly support, not meant to be pushed (at least for now). There is quite a lot missing, but there is an example which shows that it really works. And valgrind reports that all allocations were freed. The way the code is generated is also not nice, I wish there was more code actually written in some files and not generated by the generator (as much hard-coded static strings as

Hi again. I just spotted another peculiarity when inspecting the rsync log. When using --compare-dest, source files that have permissions that differ from the "comparables" are not logged, unless you're using -i. Here's a testing session: $ ls -lR .: total 12 drwxr-xr-x 2 vidar users 4096 2005-03-31 14:16 cmp/ drwxr-xr-x 2 vidar users 4096 2005-03-31 14:23 dst/

I've looked around for a bug report on this problem and haven't seen one, so I apologize if this has already been discussed. I have a homegrown script which uses rsync to maintain daily backups of roughly twenty Redhat Linux systems running RH 7.2, 7.3, AS 3, and AS 4. As there are files with multiple links on the source systems, it is necessary to call rsync using the -H (--hard-links)

Hi ! I am trying to use rsync to copy ACL between two Windows hosts. First, I try locally on a Windows hosting an AD. If I use rsync 3, I get this (I get the same thing with latest snapshot): -bash-3.2$ ./rsync-HEAD-20070703-1547GMT/rsync.exe -aAv copieA/ copieB sending incremental file list recv_acl_access: value out of range: ff rsync error: error in rsync protocol data stream (code 12) at

Yep I tried those two options, and nothing... Even if the pre-user conf files have a log file in the same directory, which I touch before trying, messages keep going to syslog... I tried with 666 permissions on rsyncd.log too just to make sure... The following is one of the user's conf file, hope theres a clue. Thanks! log file = /home/pluto/rsyncd.log <<< This is the problem!!

I've just released rsync 2.6.9pre2. This version is mainly some fixes and general cleanup that I made after getting to run the source through IBM's code checker. Please test this out and email the rsync mailing list with any questions, comments, bug reports, etc. Thanks! Here are direct links for the tar file and its signature:

I've just released rsync 2.6.9pre2. This version is mainly some fixes and general cleanup that I made after getting to run the source through IBM's code checker. Please test this out and email the rsync mailing list with any questions, comments, bug reports, etc. Thanks! Here are direct links for the tar file and its signature:

A build of rsync-2.6.9pre2 on DEC Alpha OSF/1 4.0 failed because of an undeclared variable at lib/inet_ntop.c:84: memcpy(dst, tmp, len + 1); len is not declared; the code looks like the third argument should instead be the value strlen(tmp) + 1 I made that change, restarted the build and validation, and got this report: ----- daemon-gzip-download rsyncd.log ends FAIL

Hi I am trying to get RoR to work with Postgresql 8,2.5 (latest stable version) Steps taken 1. Download Postgresql 1.82 and installed successfully 2. Edited my Database.yml development: adapter: postgresql database: test_development username: postgres password: xxx host: localhost test: adapter: postgresql database: test_test username: postgres password: xxx host: localhost