similar to: [Bug 8053] New: Older C compilers don't allow in-line declarations flist.c:1653

Displaying 20 results from an estimated 2000 matches similar to: "[Bug 8053] New: Older C compilers don't allow in-line declarations flist.c:1653"

2011 Jun 24
1
windows compilation problem
I'm compiling rsync 3.0.9pre1 using Microsoft Visual Studio 2010 on my windows XP system. I get a compilation failure in flist.c, function send_directory: flist.c(1653) : error C2143: syntax error : missing ';' before 'type' flist.c(1654) : error C2065: 'name_len' : undeclared identifier flist.c(1654) : warning C4018: '>=' : signed/unsigned mismatch
2005 Jan 31
1
[patch] add "--ignore" option
Hi, The patch below adds a "--ignore" option to rsync, which means "--exclude-but-dont-delete-even-if-we-specified--delete-excluded". I need this for a few tasks, the simplest of which is to have rsync resist trying to delete NetApp filers' ".snapshot" directories. The change is fairly simple (the boolean filter returns become tri-state), and works for me both
2011 Apr 09
1
[Bug 8073] New: Regress: 3.0.8 cannot compile on freebsd
https://bugzilla.samba.org/show_bug.cgi?id=8073 Summary: Regress: 3.0.8 cannot compile on freebsd Product: rsync Version: 3.0.8 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: blocker Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: grarpamp at gmail.com
2007 Aug 20
5
DO NOT REPLY [Bug 4899] New: When a mounted dir cannot be visited, rsync will halt there and the shell is halted, even "ctrl -c" can't quit it.
https://bugzilla.samba.org/show_bug.cgi?id=4899 Summary: When a mounted dir cannot be visited, rsync will halt there and the shell is halted, even "ctrl -c" can't quit it. Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal
2003 Aug 24
1
readdir() and read() errors ignored
We've just been hit rather badly by a very nasty bug that can cause rsync to silently discard files or fill them with zeroes. It happens when e.g. opendir() succeeds but readdir() returns an error; rsync does not check for an error from readdir() and so simply ignores the error (along with any remaining files in the directory). No error is reported to the user, who will then happily
2007 Aug 01
0
[PATCH] handle dir entries with zero length(!)
It's probably a kernel bug, and I shouldn't have tried to backup /sys on a linux system, but rsync dumped core on me due to the following: $ ls -al /sys/module/usbcore/parameters | cat -vet total 0$ drwxr-xr-x 2 root root 0 2007-07-26 18:50 $ drwxr-xr-x 2 root root 0 2007-07-26 18:50 .$ drwxr-xr-x 4 root root 0 2007-06-15 20:34 ..$ -rw-r--r-- 1 root root 4096 2007-07-26 18:50
2005 Jan 05
1
rsync filename heuristics
On 5 Jan 2005, Rusty Russell <rusty@rustcorp.com.au> wrote: > On Tue, 2005-01-04 at 18:24 +0100, Robert Lemmen wrote: > > hi rusty, > > > > i read on some webpage about rsync and debian that you wrote a patch to > > rsync that let's it uses heuristics when deciding which local file to > > use. could you tell me whether this is planned to be included in
2004 Mar 10
4
HFS+ resource forks: WIP patch included
As you all know, rsync doesn't have any special handling for Mac OS X HFS+ resource forks. Kevin Boyd made RsyncX and rsync_hfs, to address this gap, but they only work when the destination filesystem is also HFS+. I haven't been able to find any references to an rsync that is capable of syncing from HFS+ to UFS (etc). The only solutions I've seen involve lots of preprocessing
2003 Feb 16
1
rsync-exclude.patch.
> I like the idea of your rsync-exclude.patch and have thought > about hacking it in myself. However as you already have done the work > may I make a small suggestion...... can the name of the exclude file > (your .rsync) be specified in the flags.... e.g. > > rsync --rsync-exclude=.snapshot -axvH /here /there > > In this way different invocations (e.g. system and
2003 Oct 18
0
Added functionality --compare-file and --compare-auto
Recently various needs for multiple version handling were discussed and I put forward a plan of mine. Subsequently the proposal for a --compare-file=<FILE> switch had support, so I have implemented this. I have also implemented an experimental --compare-auto which decides which file to match against using a rule. Instructions for patch: 1. Install rsync-2.5.6 source 2. "patch -p1
2003 May 17
1
flist transmission and sorting
Wayne, I've been ruminating a bit on the qsorted flist and duplicate removal and have an idea. What if we removed end_file_entry() from send_file_name() and instead had a for(i=0; i < flist->count; ++i) send_file_entry(flist->files[i], f, ??) in send_file_list(). As near as i can tell this would be unnoticeable to the protocol. Once done the sort of the file list could be
2008 Jul 23
3
Trouble authenticating to Samba shares with Win 2k3 ADS
I may have a deficiency in understanding the procedure for ADS authentication with samba, but most of the server setup works so far. I have bound a Red Hat Enterprise 5 server to our windows domain, it shows up in DNS and ADS, I can ping it, but I can't get samba shares to be accessible to users, or even get the smbclient to return shares properly. wbinfo -g returns the domain groups
2007 Oct 18
1
3.0.0pre2(cvs) error: check_for_finished_files: Assertion `flist != ((void *)0)' failed.
Just a quick heads up to say I'm still getting this (reproducable) error while doing daily backups: rsync: generator.c:1872: check_for_finished_files: Assertion `flist != ((void *)0)' failed. rsync: writefd_unbuffered failed to write 4092 bytes [receiver]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1500) [receiver=3.0.0pre2] This is with cvs
2008 Mar 22
2
How does flist work
Hello Everyone, I have been reading the rsync code for the past few days and Iam finding it hard to understand how the file list works. The info that I am looking for is - "Are the files processed in the same order in both the receiver and generator processes?". Thanx in advance for all the replies. zahed. -- View this message in context:
2004 Apr 09
3
include/exclude bug in rsync 2.6.0/2.6.1pre1
As mentioned on the rsync home page, the --files-from=FILE option in rsync version 2.6.0 is a useful option that allows one to "specify a list of files to transfer, and can be much more efficient than a recursive descent using include/exclude statements (if you know in advance what files you want to transfer)". However, --files-from does not help one implement the --rsync-exclude=FILE
2003 Sep 15
0
rsync error: errors selecting input/output files, dirs (code 3) at flist.c(980)
Hi, I've got another error that is not in the FAQ ;) Ran from a script in a directory that doesn't exist anymore: shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory building file list ... pop_dir /mnt/dar : No such file or directory rsync error: errors selecting input/output files, dirs (code 3) at flist.c(980) I guess
2004 Apr 22
1
rsync problems from flist.c change
On behalf of the development team of R (www.R-project.org), I would like to report the following problem with recent versions of rsync. First, some background info. The R Development Core Team uses CVS for maintainins its source code archive. Additionally, there is a mechanism for "mirroring" some important (so-called recommended) extension packages from a CRAN (Comprehensive R
2011 Aug 27
4
[Bug 8411] New: invalid flist flag when using protocol 28 or 29
https://bugzilla.samba.org/show_bug.cgi?id=8411 Summary: invalid flist flag when using protocol 28 or 29 Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: unobe at cpan.org
2005 May 04
1
lmer error:flist must be a non-empty list
Hi, I was wondering if anyone could give me advice regarding using the lmer command in lme4 package to do logistic regression (mixed effects model). I use the following command lmer(ISH ~ArrayPathology2, random=~1|PatientID, data=HSDB4.noNA, family="binomial") where ISH is outcome(0 or 1), ArrayPathology2 is the variable of interest(factor), PatientID is random effect(factor), and
2008 Apr 22
4
DO NOT REPLY [Bug 5407] New: hlink.c:480: finish_hard_link: Assertion `flist != ((void *)0)' failed.
https://bugzilla.samba.org/show_bug.cgi?id=5407 Summary: hlink.c:480: finish_hard_link: Assertion `flist != ((void *)0)' failed. Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: