similar to: [Bug 2423] Feature Request: Ability to transfer files newer than date or file. (--newer switch).

https://bugzilla.samba.org/show_bug.cgi?id=2423 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-03-12 16:35 ------- I'd suggest using a combination of

https://bugzilla.samba.org/show_bug.cgi?id=2423 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claysjunk@digitalrum.com ------- Comment #8 from wayned@samba.org 2007-08-23 19:19 CST ------- *** Bug 3210 has been marked as a

https://bugzilla.samba.org/show_bug.cgi?id=2423 Summary: Feature Request: Ability to transfer files newer than date or file. (--newer switch). Product: rsync Version: 2.6.3 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=2423 --- Comment #10 from Rainer Glaschick <rgpb at online.de> 2014-06-04 06:56:27 UTC --- I vote for the original proposal. Using --files-from does not work with --delete, which is absolutely correct, but --newer could delete all files on the target that are not in the newer list. I use rsync for backup to large external harddisk monthly, that is

https://bugzilla.samba.org/show_bug.cgi?id=2423 pe-rsync@hindenburgring.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pe-rsync@hindenburgring.com ------- Comment #6 from pe-rsync@hindenburgring.com 2007-01-04 01:34 MST ------- I can only second

I am using outgoing call files. I typically see the "ooh something changed / timeout" on a regular bases every second to be exact. Then it stops until some other call event happens. So I "mv" my call file to the outgoing spool directory, I am listening to that message, another call file is "mv"'ed into the directory and something happens to the timeout that its

https://bugzilla.samba.org/show_bug.cgi?id=13735 --- Comment #3 from Sébastien Béhuret <sbehuret at gmail.com> --- Thank you for suggesting the patches repo. An improved checksum/maybe-checksum algorithm would be great but there appears to be a lot of work to achieve this. Checksums are very handy for special cases (e.g. to detect and fix data corruption) but are still relatively slow and

In the past there have been discussions about adding a switch to rsync to preserve the atime on files being copied by rsync. I needed this function for a project I'm working on and decided to invent it. I've attached the diffs. Note that this has the limitations describe in previous emails, namely that preserving atime causes ctime to not be preserved. *** Patch follows *** ***

It looks like I need to elaborate further to get a feedback. I checked the rsync source code and it is using utime() to restore atime file attribute. It is fine to change ctime for that transferred file in this case. What we are having problem is that when rsync gets kicked off and transfers one file to the destination, this action changes ctime of "all" files in the same

Greetings all- I am conducting security testing on a device that uses Linux 2.4 with ext3. I am testing secure overwrite of remnant data in temporary files, but have run into a real good stumpper in the way Ext allocates data blocks. I've got 10 yrs of *NIX behind me, several with Linux, and this has really got me perplexed as I can't find any documentation explaining the subject

Hi, on Windows 7 (tested on NTFS file system) and R-devel: 1. file.info("C:/") gives NAs whilst file.exists("C:/") gives TRUE. Instead you have to do file.info("C:/."). 2. Any number of dots will do, e.g. identical(file.info("C:/........."), file.info("C:/.")) == TRUE DETAILS: # C:/ => DISCREPANCY file.exists() and file.info() >

On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: >I'm trying to clone a volume in a storage pool and I'm following the steps >described here: >http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html > >My code looks like: > > destXML = """ >

This patch adds all the missing commonly used UNIX attributes: st_dev, st_ino, st_nlink, st_rdev, st_blocks, st_blksize, st_ctime. In addition it extends st_atime and st_mtime to 64bits, and adds nanosecond resolution to all three timestamps. This is implemented as an extension to the ATTR message. This patch alone is sufficient for SSHFS to be able to use these attributes. The following two

On Fri, Feb 19, 2016 at 12:33:10PM +0000, Andrei Perietanu wrote: >On Fri, Feb 19, 2016 at 12:12 PM, Martin Kletzander <mkletzan@redhat.com> >wrote: > >> On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: >> >>> I'm trying to clone a volume in a storage pool and I'm following the steps >>> described here: >>> >>>

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

On Wed 26 Oct 2016, devzero at web.de wrote: > > since we are using rsync for backing up millions of files in a virtual environment, and most of the virtual machines run on SSD cached storage, i`d be curious how that negatively impacts lifetime of the SSD`s when we do rsync run every night for backup > > my question: > does rsync normal file comparison run to determine if anything

Hi, I looked though documentation and also checked last 9 months of archives, but could not find the corresponding information. We are having an issue with incremental backup with arkeia. Arkeia checks if ctime/mtime of the file are changed, if so, it backs up. I realized that when I ran rsync from a cammnd line, it changed ctime, and preserved atime of the file in a destination as

Hi. I'm sure this is a complete green-horn question. I apologize. I'm trying to use as.Date *exactly* as shown on p. 194 of the manual (code fragment and error message pasted below). Is there some kind of "include" or "import" statement that I need to issue? Thank you very much for saving what remains of my hair. > x <- c("1jan1960",

I'm trying to understand why as.Date() is converting a the modified date of a file from August 22 to August 23. > foo <- file.info(file.to.process) > str(foo) 'data.frame': 1 obs. of 10 variables: $ size : num 5.37e+09 $ isdir : logi FALSE $ mode :Class 'octmode' int 436 $ mtime : POSIXct, format: "2010-08-22 23:14:52" $ ctime : POSIXct, format: