similar to: DO NOT REPLY [Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #24 from Karl O. Pinc <kop at meme.com> --- On Sun, 06 Mar 2016 22:20:16 +0000 samba-bugs at samba.org wrote: > https://bugzilla.samba.org/show_bug.cgi?id=2294 > > --- Comment #23 from dajoker at gmail.com --- > Looking for this capability prior to entering it as an enhancement > request myself, I found everything

https://bugzilla.samba.org/show_bug.cgi?id=2294 boris@folgmann.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |boris@folgmann.de ------- Comment #6 from boris@folgmann.de 2007-07-11 09:50 CST ------- I'm using rsync 2.6.9 to archive rotated

https://bugzilla.samba.org/show_bug.cgi?id=2294 ------- Comment #12 from phr-samba at nightsong.com 2011-01-28 20:38 CST ------- Hi, I was about to enter a similar suggestion to this. My very frequent use case is moving files from one directory to another. In that situation the file name does not change--just the directory path leading to it. These are often quite large files (0.2 to

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #25 from Andrey Gursky <andrey.gursky at e-mail.ua> --- On Sun, 06 Mar 2016 22:20:16 +0000 samba-bugs at samba.org wrote: > https://bugzilla.samba.org/show_bug.cgi?id=2294 > > --- Comment #23 from dajoker at gmail.com --- > Looking for this capability prior to entering it as an enhancement request > myself, I found

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #23 from dajoker at gmail.com --- Looking for this capability prior to entering it as an enhancement request myself, I found everything here and basically have the same use case. My version is that I am creating a regular backup of logs from many servers' services onto a single box, and doing so with rsync. Some of those services

https://bugzilla.samba.org/show_bug.cgi?id=2294 ------- Additional Comments From blackb1rd@seat-ibiza.nl 2005-02-11 01:58 ------- I totally agree this one. With this enhancement there would be no longer unnecessary traffic when some user has moved / copy'ed a large directory (which is really annoying). -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #20 from kevin.layer at gmail.com 2014-03-02 03:08:37 UTC --- I've been playing with the --detect-renamed patch https://git.samba.org/?p=rsync-patches.git;a=blob;f=detect-renamed.diff;h=c3e6e846eab437e56e25e2c334e292996ee84345;hb=master I can't get seem it to work. Does it rely on other patches? Anyway, in a simple test, using

https://bugzilla.samba.org/show_bug.cgi?id=2294 Summary: Detect renamed files and handle by renaming instead of delete/re-send Product: rsync Version: 2.6.3 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #26 from Ben RUBSON <ben.rubson at gmail.com> --- ### What's the diff between --fuzzy and --detect-renamed ? If I understand correctly, --fuzzy looks only in destination folder, for either a file that has an identical size and modified-time, or a similarly-named file, and uses it as a basis file. Whereas --detect-renamed looks

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #27 from Wolfgang Hamann <wolfgang at maas-noten.de> --- Hi, I recently ran into the problem that a large file set got renamed and then re-sent. I tried to fix after the fact, so I went the obvious way of comparing sizes and modtimes on the destination and calculate checksums for potential matches. I would have preferred to use a

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #40 from roland <devzero at web.de> --- > This feature request is so old it has lost relavence because btrfs/zfs/etc are more optimal backup solutions than rsync. sorry, but this comment is totally nonsense, as btrfs and zfs are filesystems (i.e. places to store data) whereas rsync is a tool to sync data from one place to

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #41 from Mihnea-Costin Grigore <mihnea at zulu.ro> --- The discussion about file systems like ZFS/BTRFS/etc. and their various snapshot mechanisms is off-topic relative to this feature request, since they are very different technologies used for different purposes. rsync is used commonly to synchronise at the *file level* between

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #22 from elatllat at gmail.com --- Wow 10 years. Maybe one reason this has not been implemented is there are other options. For example I have been using a shell script as a wrapper to reduce the iteration of this bug, here is how it works: 1) Create 2 lists of files; destination and source with the files sizes and path 2) For each file

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #39 from andy <andy at digitalsignalperson.com> --- > This feature request is so old it has lost relavence because btrfs/zfs/etc are more optimal backup solutions than rsync. Funny I am doing exactly this, but I came to rsync looking for a backup for when ZFS fails. Many consider zfs/btrfs/snapshots as "not a backup".

Ever since a recent power failure I have been getting a Logrotate error. My machine is on a UPS -- it shutdown cleanly, but I suspect that its BIOS/RTC battery is dead, since the machine came up thinking it was 1982 :-(. I reset the clock and everything is fine, *except* I had to delete Logrotate's state files (which had bad dates). But now Logrotate is raising the error: error: error

Hi all, I have a problem with logrotate and I don't know why. In /var/log/messages appears these errors: Apr 8 15:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 16:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 17:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 18:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8

Package: logcheck Version: 1.2.58.0 Severity: wishlist Tags: patch The attached patch is the diff from current svn trunk to my svn branch zugschlus200707. It introduces a new binary package logtail2 with a new binary logtail2 which enhances logtail substantially. logtail2 can process rotated logs internally, which makes the code inside logcheck and other programs that use logtail2 easier to

Anyone having problems with logrotate and CentOS 5.4? Although I have /etc/logrotate.d/mail (contents below) to rotate my maillog file, it fails to do it automatically: /var/log/maillog { compress dateext maxage 365 rotate 60 size=+1024k missingok postrotate /etc/init.d/MailScanner restart endscript } ++++++++++++++++++++++++++++ logrotate.conf:

Hi! I have one problem with my logrotate. Samba version: Samba 4 7.7 (compilated) S.O.: Ubuntu 14.04 /16.04 Samba logs file: /opt/samba/var/ Logrotate File: cat /etc/logrotate.d/samba -- /opt/samba/var/log.samba {   rotate 10         daily         compress         dateext         size 100M         nomail         missingok         notifempty         create 644 root root

Am 14.05.2018 um 21:08 schrieb Reindl Harald via samba: > Am 14.05.2018 um 20:56 schrieb Carlos via samba: >> /opt/samba/var/log.samba >> >> { >>   rotate 10 >>         daily >>         compress >>         dateext >>         size 100M >>         nomail >>         missingok >>         notifempty >>         create 644 root