similar to: Problem using --fuzzy with --*-dest flags

Hi, I'm having a problem trying to get the --debug flags to work with 3.1.0. I wanted to check with the mailing list to make sure this is really a bug and not something I'm misunderstanding. This is what I'm running (as a test): rsync --fuzzy --fuzzy -vv --debug=FUZZY,FUZZY2 C_VOL-b001-i3818.spi rsync://user at localhost/SHARENAME/dest The "dest" folder on the destination

I've identified a situation where the combination of --fuzzy --fuzzy (yes: two of them) and --link-dest is not behaving as I'd expect. I'm first wondering if my expectation is wrong. Assuming that it is not, then I'm wondering how best to figure out the problem. The double use of --fuzzy is based upon https://bugzilla.samba.org/ show_bug.cgi?id=4056 which should be present on

Am Samstag, dem 11.03.2023 um 19:30 +0100 schrieb spi: > > 11.03.2023 19:23:21 Benny Pedersen <me at junc.eu>: > > > spi skrev den 2023-03-11 13:34: > > > > > if address :domain "From" "whatever.com"{ > > > fileinto :flags ["\\todo"] "working/whatever"; > > > } > > > > require

I've been reworking my backup script & decided to give some of the newer options a try. It would appear I've found a combination that doesn't play nice. $ rsync --archive --delete-during --fuzzy --hard-links --numeric-ids --quiet --sparse --temp-dir /backup/helium/ --link-dest /backup/hydrogen/tuesday/ --password-file /backup/helium/.password rsync://backup@helium/backup/

https://bugzilla.samba.org/show_bug.cgi?id=4056 Summary: Option to look for fuzzy basis files in --*-dest directories Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

Hello, I use --link-dest which works perfectly : rsync -a -R --link-dest="../2016-12-28/" --link-dest="../2016-12-27/" /my/backup/folder ::daemon/mycomputer/2016-12-29/ Now I would like to use --fuzzy --fuzzy, so that rsync algorithm can also work with similarly named files found in other link-dest directories. So I simply added --fuzzy --fuzzy to my previous command line.

Hi! Does --fuzzy also look for files in dirs mentioned with --...-dest? My special intrest lies in --link-dest, though. Thanks, Robert

Dear all, I have a problem in writing a variable to a NetCDF-File. My code works pretty well until the step put.var.ncdf(): # Get variables #--------------------- data1 <- open.ncdf("PREC_me_03-1500.nc") prec1 <- get.var.ncdf(data1,"PRECT") dim.time <- get.var.ncdf(data1,"time2") close.ncdf(data1) # Calculation #--------------------- spi24.me <-

I am working with implementing Asterisk between four different AS5400's located in multiple sites with different PSTN gateways. I can get two of them to work without a problem, but I am getting the following on the others when I make a SIP call to the other two sites. Got SIP response 500 "Internal Server Error" back from 10.1.3.28 SIP/alma-1b77 is circuit-busy Everyone is

https://bugzilla.samba.org/show_bug.cgi?id=13445 Bug ID: 13445 Summary: Fuzzy searching in link-dest tries to open regular file as directory Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Hello all, I am about to send off a manuscript and, although I am fairly confident I have used the lme function correctly, I want to be 100% sure. Could some kind soul out there put my mind at ease? I am simply interested in whether a predictor (SPI) is related to height. However, there are five different populations, and each may differ in mean level of height as well as the relationship

hello i am trying to set up ipsec in my network, for now just between two hosts, using to use AH & ESP in tunnel mode to get all of packet encrypted. keys are negotiated with racoon. mayby using tunnel mode in this case can seems strange, but i know what i am doing. after setting up everything i have done few tests with ping & tcpdump. but the results are very suprising. bellow is what i

Hello everyone, This set will switch the users of pm_runtime_put_autosuspend() to __pm_runtime_put_autosuspend() while the former will soon be re-purposed to include a call to pm_runtime_mark_last_busy(). The two are almost always used together, apart from bugs which are likely common. Going forward, most new users should be using pm_runtime_put_autosuspend(). Once this conversion is done and

Here's my sip debug output. anybody knows why Cisco sent * is CANCEL msg? Can someone tell me what ATA version are they using? Maybe this is also another issue.. I am using v2.16. This is using G711ulaw. Sip read: > SIP/2.0 100 Trying Via: SIP/2.0/UDP asterisk:5060;branch=z9hG4bK13fbce3e From: "Jess" <sip:6882332@mydomain.com>;tag=as6818ebfb To:

I am trying to set up an ipsec net-to-net VPN and am having problems. Here is a diagram of the setup: LAN A --> Host A ----> Internet <---- Host B <-- LAN B LAN A = 10.10.2.0/24 LAN A gateway = 10.10.2.254 Host A internal = 10.10.2.254 Host A external = xx.xx.xx.xx Host B external (see below) Host B internal = 10.10.1.10 LAN B = 10.10.1.0/24 LAN B gateway = 10.10.1.252 (F5 Big

http://bugzilla.netfilter.org/show_bug.cgi?id=577 Summary: cannot set spi/reqid numbers higher than 0x7fffffff (policy match) Product: iptables Version: unspecified Platform: i386 OS/Version: All Status: NEW Severity: normal Priority: P1 Component: iptables AssignedTo: laforge

11.03.2023 19:23:21 Benny Pedersen <me at junc.eu>: > spi skrev den 2023-03-11 13:34: > >> if address :domain "From" "whatever.com"{ >> fileinto :flags ["\\todo"] "working/whatever"; >> } > > require ["fileinto","imap4flags"]; imap4flags seems not to be accepted in an user script. My sieve editor

Hi All, I need to establish an IPSec tunnel between two FreeBSD systems, using IPv6 addresses.The connetcion is host-to-host between two FreeBSD( RELEASE 4.11) systems with KAME IPSec implementation. I tried to establish the connection, but it has some problems which are explained below. |----------------->| host1-[mohan]| |host2-[ram]

Hello, How do I find out what is happening to my packets thru my ipsec tunnel. They just seem to disappear on the remote side. I have successfully got the pings thru when everything has an ipv6 address, but am not successful when trying to connect two ipv4 lans across an ipv6 ipsec tunnel. All fw chains both 4 and 6 are set to ACCEPT. NAT is turned off. eth0 eth1

Has anyone built this on Tru64 Unix? I downloaded and attempted to build today and received this, # /usr/sbin/sizer -v HP Tru64 UNIX V5.1B (Rev. 2650); Tue Mar 20 15:08:40 CDT 2007 # # make Using FLAGS = -O -D_SAMBA_BUILD_=3 -I/usr/local/include -I/spi/opensource /samba-3.0.25c/source/iniparser/src -Iinclude -I./include -I. -I. -I./lib/repla ce -I./lib/talloc -I./tdb/include -I./libaddns