search for: changedfiles

In a number of places internal to R, we need to know which files have changed (e.g. after building a vignette). I've just written a general purpose function "changedFiles" that I'll probably commit to R-devel. Comments on the design (or bug reports) would be appreciated. The source for the function and the Rd page for it are inline below. ----- changedFiles.R: changedFiles <- function(snapshot, timestamp = tempfile("timestamp"), file.info...

Hi rsync gurus! [Please Cc: me, as I am NOT subscribed to the list!] First the data points: debian/woody, local server=i386 arch, remote is alpha arch rsync version on both debian 2.5.5-0.2 While upgrading our server to a raid we were hit by a bug which I really consider very strange: The option -n/--dry-run does NOT change files, but DELETE files when called with --delete. Test case I had: $

Apologies in advance for a kind of long question: I've written an application called changedfiles (http://www.bangstate.com/software.html#changedfiles), which consists of two parts: a linux kernel module that reports all file operations to a device special, and a userspace daemon which can take arbitray shell action on files matching regexp rules specified in a config file. E.G., to...

...quence of changes elsewhere in Sweave processing or in the handling of R in BATCH mode. > When watching the folder where the file output activity takes place, I note that a file .build.timestamp is created and then deleted, which leads me to believe that the new functions fileSnapshot() and changedFiles() are being used in the course of processing R in BATCH mode. If that is correct and there is a clean up step that is occurring upon BATCH mode exit, which deletes all files and folders other than .tex files, is it possible that this process is being overly aggressive? Or if not, is there a way to...

...aven't yet managed to solve this issue. rsyncing from Mac OS X to FreeBSD and from Linux to Windows XP, with the arguments avz I get the same thing in the reports (mailed from cron): path/ path/to/ path/to/directories/ path/to/directories/changedfile.txt another/path/ another/path/withoutanychangedfiles/ yet/anotherpath/ yet/anotherpath/withoutanychangedfiles/ ... and so on. With biggish directories this results in huge lists which have to be trawled through if manual checks are to be made that changed files were successfully copied/updated. I have a feeling that this stems from differences in...