similar to: looking for encrypted rsync

> On 25 May 2020, at 23:55, Wayne Davison via rsync <rsync at lists.samba.org> wrote: > > I've decided to give hosting it on github a try, especially since there's been a lot of nice contributions lately. Hopefully this will make it easier for both the people sending patches as well as for me to snag the changes. I'll continue to push changes to the samba git as well.

problem is he's trying to rsync into the target dir and have the side effect of delete. so an empty dir would necessarily need to be in the target of course and thus created there, triggering the quota block. he tried to avoid this by using device files then 'blocking all device files' but i think rsync figures out first there's nothing to do, so it just stops and doesnt do the

Hi Ram, In OS X, some font types (not all) put the font payload in the resource fork. Netatalk provides AFP filesharing, imitating the resource forks by creating secondary files in ?.Appledouble? folders within each folder. Netatalk tracks the resource forks, and other metadata, by keeping a ?Desktop database? at the root of the shared volume ? look for .AppleDesktop, and .AppleDB. You can

There are times when a large file is copied up to 99% and then deleted after having received the error. Other times when the error occurs earlier and only a part of it is copied. Does it make sense to calculate the checksum if in both cases in output I don't have the same information that there is in input ? Because in the first case it is totally deleted and in the second case I have only a

Anyone have any other ideas I could try to debug this issue? :) -- Best regards / Met vriendelijke groet, Aron Rotteveel 2015-03-27 16:02 GMT+01:00 Aron Rotteveel <rotteveel.aron at gmail.com>: > Hi Kevin, > > Just did: same result. > > -- > Best regards / Met vriendelijke groet, > > Aron Rotteveel > > 2015-03-27 14:32 GMT+01:00 Kevin Korb <kmk at

Not to mention the fact that ZFS requires considerable hardware resources (CPU & memory) to perform well. It also requires you to learn a whole new terminology to wrap your head around it. It's certainly not a trivial swap to say the least... Thanks, -Clint On Mon, Apr 6, 2015 at 9:12 AM, Ken Chase <rsync-list-m829 at sizone.org> wrote: > This has been a consideration. But it

I've decided to give hosting it on github a try, especially since there's been a lot of nice contributions lately. Hopefully this will make it easier for both the people sending patches as well as for me to snag the changes. I'll continue to push changes to the samba git as well. Here's the new repo: https://github.com/WayneD/rsync Feel free to open issues there, but we

Exit code 2 is "Protocol incompatibility". Also, sounds like what you really want is --files-from On 04/07/2017 10:01 AM, Axel Kittenberger via rsync wrote: > With this two options on a very live system you may need to take into > account this bug as well I reported a while ago: > > https://bugzilla.samba.org/show_bug.cgi?id=12569 > > Due to this I'm currently

Hi Kevin, Just did: same result. -- Best regards / Met vriendelijke groet, Aron Rotteveel 2015-03-27 14:32 GMT+01:00 Kevin Korb <kmk at sanitarium.net>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Try it without any --delete options. > > On 03/27/2015 09:31 AM, Aron Rotteveel wrote: > > I am now running with --delete --numeric-ids --relative but the

Problem was introduced with this commit: commit f3873b3d88b61167b106e7b9227a20147f8f6197 Author: Wayne Davison &lt;wayned at samba.org&gt; Date: Mon Oct 10 11:49:50 2016 -0700 Support --sparse combined with --preallocate or --inplace. The new code tries to punch holes in the destination file using newer Linux fallocate features. It also supports a --whole-file

>Almost certainly your drive is going bad. On Linux I'd tell you to check dmesg for drive errors, I don't know what the FreeBSD equivalent is. But I strongly recommend that you treat that drive as "going to fail any second". I'm not sure that this is the reason. I see the error regardless of the USB disks that I use. And I have a lot of USB disks,10 disks. No,I

On Wed, Dec 3, 2014 at 9:40 AM, Tomasz Chmielewski <mangoo at wpkg.org> wrote: > rsync in daemon mode is very powerful, yet it comes with one big > disadvantage: data is sent in plain. > > The workarounds are not really satisfying: > > > - use VPN - one needs to set up an extra service, not always possible > > - use stunnel - as above > > - use SSH - is not

Why are you encrypting the files and not the filesystem and the channel? On Tue, Oct 13, 2015 at 6:54 PM, Xen <list at xenhideout.nl> wrote: > Hi Folks, > > I was wondering if I could ask this question here. > > Initially when I was thinking up how to do this I was expecting block > encryption to stay consistent from one 'encryption run' to the next, but I >

On Wed, Apr 22, 2015 at 9:15 AM, Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Normally, I would say that --checksum is actually slower than just > letting rsync re-copy everything Depends on the network capacity and costs associated with that bandwidth :( >and therefore is almost always the > wrong thing to do. Nope,

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

Sent from BlackBerry? on Airtel -----Original Message----- From: rsync-request@lists.samba.org Date: Sun, 28 Oct 2007 12:00:33 To:rsync@lists.samba.org Subject: rsync Digest, Vol 58, Issue 29 Send rsync mailing list submissions to rsync@lists.samba.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.samba.org/mailman/listinfo/rsync or, via email, send a message with

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

The errors column is 0. The drop column is 18. The second bit number is the number of packets which should grow. At least that is how I read it. Column makes it more readable in a terminal but not so much in an email. On 12/21/23 14:18, Alex wrote: > Can someone help me determine if these errors are normal or if this > could somehow be the cause? I've removed the last three

What would you think if I told you that using Windows I no longer had that problem ? Would you still think that there are hardware problems ? And if so, why would they only manifest themselves using Linux and FreeBSD and not using Windows? On Mon, Dec 23, 2024 at 9:38?PM Robin Lee Powell < rlpowell at digitalkingdom.org> wrote: > Then you get to look at other hardware; CPU, RAM,

Steve Sills Platnum Computers, President http://www.platnum.com steve@platnum.com ----- Original Message ----- From: "Steve Sills" <steve@platnum.com> To: "jw schultz" <jw@pegasys.ws> Sent: Thursday, January 22, 2004 1:52 PM Subject: Re: Rsync's Speed > The source server is a Dual 800 Mhz /w a 7200 RPM 40 GB HDD, the dest server > is a P III 450 with a