similar to: How does flist work

Hey everyone, I am a final semester MCA student. I've chosen rsync as the subject of my project for my graduation. Hence I would appreciate it if someone could guide me with some ideas on how I can contribute to rsync. I will work hard to implement whatever suggestions that you can all give me. I would definitely like to know what are some of the issues concerning rsync. May be I can then

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:

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

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

Ok, I just setup the log file and this is what I see there: rsync on cdrive/Temp/pix.log from admx (141.214.137.139) transfer interrupted (code 3) at flist.c(812) I had to change [cdrive] from path = "c:\" to path = c: to get rid of '@ERROR: chdir failed' error. I am getting close but still need some help. Thanks in advance. Nishi > -----Original Message----- From:

Hello all, Thanks for all the ideas. I liked the remote to remote idea and have told my guide about it. Anyways, can anybody tell me which files to look into, if I want to look at the code for file reconstruction. I have studied Dr. Tridgell's thesis on the Rsync Algorithm and have understood the working of the algorithm. Now, I am trying to read the code to understand it better. Any help

https://bugzilla.samba.org/show_bug.cgi?id=8053 Summary: Older C compilers don't allow in-line declarations flist.c:1653 Product: rsync Version: 3.0.8 Platform: All OS/Version: FreeBSD Status: NEW Severity: minor Priority: P5 Component: core AssignedTo: wayned at samba.org

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

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

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

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

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

Hi, I have loaded a dataset in R : data = label freq1 freq2 news 54 35 fun 37 21 milk 19 7 food 3 3 .... etc And I have a vector flist<-c("fun","food") Now I want to use the vector 'flist' for selecting these values from 'data' so that I get the following dataset : label freq1 freq2 fun 37 21 food

The first patch will make "make install-strip" work. The second spends a few cycles avoiding "1 files to consider." Both are trivial but IMHO useful. --- Makefile.orig Wed Mar 13 06:38:42 2002 +++ Makefile Wed Mar 13 06:40:58 2002 @@ -12,6 +12,7 @@ LDFLAGS= INSTALLCMD=/bin/install -c +INSTALLMAN=/bin/install -c srcdir=. @@ -56,8 +57,8 @@ ${INSTALLCMD} -m 755 rsync

Hello, first of all, thanks to LT for \pkg{codeutils}. I agree that it is indeed very useful to identify errors and also to encourage re-thinking past solutions. My problem: I want to compare different sets of related sub-functions which should be used alternatively by the same top-level function. Sets of related functions should be bound together (as lists) and the workspace should be as clean

Hi, The problem I found is not in what rsync, but on the error handling: How to reproduce: On server side I setup a tree and share using rsync + xinetd, of course, for security reason I use chroot option. Now I push this symlink: lrwxrwxrwx 1 root root 4 nov 10 16:28 horsroot -> /bin/ Now I try to do: ./rsync -avPH --copy-unsafe-links draco::test/ /tmp/rsyncdest/ (Of course the

Hi guys. I recently stumbled on an unexpected behavior of R when using functions created in a loop. The problem is silly enough to me that I had hard time choosing a good mail subject, not talking about searching in the archives... After some experiments, I trimmed down the following minimal reproducible example: ####### makeF <- function(i) function() i fList <- list(makeF(1), makeF(2))

I'm getting a SEGV on a FreeBSD 4.8-STABLE box. The client is Solaris 9/SPARC. Both boxes run 2.6.2. The command I'm running is: $ rsync -arHRv --numeric-ids --delete --exclude=/opt/dist/cdrom \ [paths] [server]:[path] If I whittle down what appears in [paths], then it works. $ gdb rsync rsync.core gdb> bt #0 0x280faf0d in strncmp () from /usr/lib/libc.so.4 #1 0x7 in ?? () #2

Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a

Hi, I have many .txt files which look like this: 2009/02/07 12:30:10.0 ? ? ?5.0161 ? ? ?13.208 2009/02/07 12:45:10.0 ? ? ?5.0102 ? ? ?13.350 2009/02/07 13:00:10.0 ? ? ?5.0044 ? ? ?13.473 .... .... .... 2009/02/07 16:30:10.0 ? ? ?4.9366 ? ? ?13.788 2009/02/07 16:45:10.0 ? ? ?4.9397 ? ? ?13.798 end data. ###I can read in all files from "my_folder" using the following code: