similar to: Newbie question.

I've now got scripts that correctly backup all my primary partitions to a second drive. The original problem was that I copied them over without a time stamp, so that the first rsync run found no timestamps and wanted to copy them all over again. So I used: 'rsync -r -t -v --size-only $SOURCE $TARGET' My question is this: do I need to continue to use --size-only, or has the

Hi... trying to install Codeweavers-wine-20010305, which is the latest stable build I understand. It configures and then informs me that it'll compile but that building without the Xpm development files won't work. Sure enough... they were right...<grin> So I go get the latest Xpm stuff and they turn out to be libxpm4-3.4 and libxpm4-devel-3.4. Got them in .src.rpm and

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

Hello everyone! FOREWORD: I respect your time and resources, I hope to not bother people on this mailinglist! To my defense: This question is far easier towards humans than to mailinglist and web search-engines as the search terms in relation to each other are highly in-causal or paradoxical, and hence lead to poor results. Of course the manpage was the first place where I looked

Please, is possible (with rsync) re-create files timestamps? I mean something like choosing a "-T" in the program mirror- from it's man page e.g. there: http://sunsite.univie.ac.at/textbooks/mirror/mirror.html#Flags "Do not do any file transfers just force the time-stamps of any local files to be reset to be the same as the remote files. Normally only used when initialising a

Greetings - I am trying to document the "value" section of a function. The function returns a list, but the list itself also has attributes. I would like to itemize the list entries, and itemize the attributes, but in between I would like to have a sentence or two about the attributes in general. However, for some reason this intermediate sentence won't show up in the compiled

Hi, I am facing a strange situation with my daily backups performed via rsync. I primarily use Manjaro KDE Linux (LTS kernel), but also have FreeBSD and Windows 10 bare-metal installations. I have an all-OS-writable ext2 partition /dev/sda2 mounted at /mnt/wall My USB backup device is a Sony SSD mounted at /mnt/sony This is the relevant line from my script which backs up /mnt/wall : rsync

IIUC, the new philosophy of symlink times is that -t preserves them to the extent that they are settable; when they aren't, it's just as if -t wasn't given. But rsync breaks this principle in the following case. Suppose rsync is configured with HAVE_LUTIMES enabled but the lutimes call doesn't actually work (I simulated this via the attached patch). When rsync recreates a

Hello, I have a question about how/why rsync updates modification times, which I haven?t been able to find an answer to. I have two locally connected storage devices running TrueNAS Core: one is new and empty, while the other is filled with files. When I run the following rsync command: rsync -avPh --itemize-changes --stats "${@}" to transfer files from the full storage to the empty

You are using rsync -a which copies (preserves) the timestamp. Meaning that rsync will copy the file then back-date it to the timestamp of the source file. Most copying tools do not do this though cp's -a does it too. Note that your itemized output says that the timestamp is different meaning that the file has changed since rsync last ran. Without the -a (or the included -t) the

Hi Kevin, The -a flag in this instance is not back-dating the timestamp of the copied file to the source file. It is modifying it to the time of transfer and leaving it that way. Then any time I rerun that command it always updates the timestamp since it is always making it the time of transfer. I have a source file the has a modification date of 2015 and when I rsync it to day with -a the copied

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No, even if bandwidth is your concern I would say that --checksum is wrong. Maybe if bandwidth is so scarse that a few KB vs a few MB equates to dollars then sure, use --checksum. Otherwise, letting rsync re-delta-xfer everything is certainly faster and not much more bandwidth intensive than --checksum. Plus that is only if you screwed up and ran

That isn't how rsync should work with -a. Is something preventing it from backdating the file? What is the filesystem? Can you try copying your 2015 file with cp -a? On 10/9/24 14:56, McDowell, Blake wrote: > Hi Kevin, > > The -a flag in this instance is not back-dating the timestamp of the > copied file to the source file. It is modifying it to the time of > transfer

On Mon, Mar 28, 2016 at 08:11:07AM -0400, Kevin Korb wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What does --itemize-changes say about these files? > > Also, what is --atimes? Is this the Apple modified rsync for OSX? > > On 03/28/2016 07:51 AM, Albert Berger wrote: > > Greetings, > > > > when the daily system backup with rsync is

Hello all, I am new to puppet and I currently just use it during development - just two hosts. I only manage distribution of files/permissions with it. I am wondering why puppetd is running slowly on one of these machines. Google told me that File with "recurse => true" will make things run slowly. I use "recurse => true" :( Now I want to find out now if the slowdown I

We have NFS mounted drives. I first build an clang/llvm hosted compiler for Mips linux using the clang/llvm linux x86 compiler. Call this clang1. then in directory recurse on Mips host, I place this clang1 compiler and build clang2. then i rename recurse to recurse1 and create a new recurse directory. in recurse I copy clang2 from recurse1 to a recurse but name it clang1. then i build

I am new to SAMBA and I have what I'm not even sure is an issue. I am aware of the difference in time stamps between *nix and Windows. What I don't understand is this: I used touch to modify the time stamps of a large number of files on the file server from the server side to match the time in the file name. They were video files from my Digital Video Cam and the import program used

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would need to see both your existing rsync command line and the output of --itemize-changes when such an occurrence happens before I can really understand what is happening. In the end, if you have any output at all the bare minimum should be - --itemize-changes. --verbose is utterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: >

Please be gentile ... I am new at this ror thing I have a view which looks like this <h1>Nicaragua Stamps</h1> <table id ="stamps"> <tr> <th>Scott</th> <th>Maxwell</th> <th>Description</th> <th>Url</th> <th>Mint</th> <th>Used</th> </tr> <% @stamps.each

I've just released rsync 3.0.0pre10. I incorporated the latest daemon security fixes, and decided to include a few more minor bug fixes as well. If all goes well, this should be released as 3.0.0 final sometime next week. Please help to test it to ensure that we're ready to go! Send email to the rsync mailing list with your questions, comments, bug reports, etc. You can download the