similar to: rsync file sync by priority

Dear all is it possible to rsync in a master-slave scenario saving to slave gzip content? i'm not talking about compression during transfer, i'm talking about -saving- the destination in a compressed format. Example: FROM: -folder_A --file_A --file_B TO: -folder_A --file_A.gz --file_B.gz I know that this won't be a "real" rsync between two folder, but it will be an

I am using llvm for source-to-source inlining. So I did: % llvm-gcc file_a.c file_b.c ... file_n.c -o file % opt -inline -inline-threshold=1000 < file.bc | llc -march=c > outfile.c Can anyone tell me how llvm determines if a function should be inlined, and what roll does "inline-threshold" play ? (Does the example mean that if the function body has fewer than 1000 instructions,

Hi *, it seems rsync with --fileflags isn't able to work on (already) hardlinked and immutable ("schg") files on FreeBSD. The following scripts will create a simple example for this behaviour: -------------------------------------------------------------- #! /bin/sh # # set -x DIR="/var/tmp/rsync_$(date +%s)/" mkdir "${DIR}/" # Preparing dir_A mkdir

I have a volume at 192.168.0.2 on my local network. I'd like to rsync the entire volume to a backup volume, skip all files already present on the backup volume (same name and the same or earlier timestamp), and include all flags, dates, etc. as applicable to Mac OS X 10.6.x. Can someone tell me the proper command to do this.

An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20091030/c43a29f5/attachment.html>

https://bugzilla.samba.org/show_bug.cgi?id=2554 ------- Additional Comments From wayned@samba.org 2005-03-29 11:50 ------- (In reply to comment #0) >> If a file will be deleted the line starts with "Delete", but when a > file will be copied or overwritten, nothing is displayed. I assume you mean, "no prefix is displayed" since there is something that is

Hi, What''s happening here? require ''windows/path'' require ''windows/unicode'' include Windows::Path include Windows::Unicode file_a = ''bar.txt'' file_w = multi_to_wide(file_a) p PathFindExtensionA(file_a) # ''.txt'' => OK p PathFindExtensionW(file_w) # ''.'' => WRONG Is Ruby chopping the

On Mon, Jul 04, 2005 at 03:32:39PM -0500, Long Fei wrote: > I am using llvm for source-to-source inlining. So I did: > > % llvm-gcc file_a.c file_b.c ... file_n.c -o file > % opt -inline -inline-threshold=1000 < file.bc | llc -march=c > outfile.c > > Can anyone tell me how llvm determines if a function should be > inlined, and what roll does

Hi, I am looking for a way to save the result of a function, e.g the lm()-function to a file and reload it afterwards again. I'd like to do that in order to minimize the used memory when running the function in a loop. The actual function I want to store is the evaluate() from the dismo package. I tried it with save() and load() but I am not sure if that is the way I should do it as I

Hello guyz! I'm new here, and this is my very first truble... I need a script that will backup & compress the folder /media/system in the folder /media/backups But that's not the problem, I need that only the last 7 backups (last 7 days, yeah I know, cronjob...) will stay in that folder... The script need: 1 - Compress folder /media/system 2 - Store in /media/backups 3 - Name the

Get also the fd for the tar subprocess, and drain and print its content if the tar invocation fails. --- src/copy-in-out.c | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 61 insertions(+), 4 deletions(-) diff --git a/src/copy-in-out.c b/src/copy-in-out.c index dc9e7b7..0dd8cd3 100644 --- a/src/copy-in-out.c +++ b/src/copy-in-out.c @@ -34,17 +34,19 @@ #include

struct timespec64 has unused bits in the tv_nsec field that can be used for other purposes. In future patches, we're going to change how the inode->i_ctime is accessed in certain inodes in order to make use of them. In order to do that safely though, we'll need to eradicate raw accesses of the inode->i_ctime field from the kernel. Add new accessor functions for the ctime that we can

I've been working on a patchset to change how the inode->i_ctime is accessed in order to give us conditional, high-res timestamps for the ctime and mtime. struct timespec64 has unused bits in it that we can use to implement this. In order to do that however, we need to wrap all accesses of inode->i_ctime to ensure that bits used as flags are appropriately handled. This patchset first

hi everybody this happens when a Domain Admin adds a user-permission set via properties/security in Windows folder_A was created by a Domain Admin new permission - Modify - was added over the folder_A to the user_A user_A created a file_A.txt in folder_A now Domain Admin goes back to the properties of folder_A wanting to change/modify security entries operation fails on windows: "An

I'm trying to switch to using rsync for updating a huge software library containing binaries, text files, symlinks, and so on. We've been using something homegrown which I'm not that happy with - it's a perl script that systems cp and chmod and such. The problem I'm seeing is: target computer: directories ctime-5 and ctime-5b3 are distinct directories source computer:

On Tue, Sep 29, 2015 at 11:38:52AM +0200, Pino Toscano wrote: > --- > src/copy-in-out.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/src/copy-in-out.c b/src/copy-in-out.c > index 0dd8cd3..2b1e4d4 100644 > --- a/src/copy-in-out.c > +++ b/src/copy-in-out.c > @@ -47,6 +47,12 @@ guestfs_impl_copy_in (guestfs_h *g, const char *localpath, const char

(R 2.8.0 on Debian GNU/Linux sid) ?file.info contains: mtime, ctime, atime: integer of class '"POSIXct"': file modification, creation and last access times. This implies that ctime is "file [...] creation [...] time" Has R implemented ctime differently to Unix? I understand, on Linux at least, that ctime is the last change time (not the creation time).

On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> wrote: Hi Kevin. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The ctime will always be newer or the same as the mtime. This is > because changing the mtime also changes the ctime as does other things > like changing the permissions. > > Rsync only pays attention to the mtime because rsync can

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

$ /usr/sbin/dovecot --exec-mail ext expire-tool --test Info: Trash: timestamp 1243963680 (Tue Jun 2 19:28:00 2009 ) -> 1244307774 (Tue Jun 2 19:28:00 2009 ) Both human readable timestamps are equal as ctime() returns a pointer to a static buffer. In addition there are some newline characters added by ctime(). The following patch is a try to fix this for 1.2.rc5. --- expire-tool.c.orig