similar to: No subject

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was actually in the include/exclude section of the man page not the filter section. However, your syntax does work. The +/- syntax absolutely works in an --exclude-from or --include-from file I use it all the time. However, apparently the -/ syntax does not work there. So, I am not sure if the man page is wrong or if this feature just isn't

Patch includes fixes to man page including: - Typos/Spelling - Clarity - Special characters. - Moved around text explaining example. Make sure I didn't confuse the exclude list/file paragraph (line ~961 after applying the patch), I haven't used the feature and the motive of that paragraph is a tad unclear. Hope the patch is helpful. Never had used yodl before. Thanks for rsync. /a

There are two security advisories for people who run a writable rsync daemon. One affects only those with "use chroot = no" (which is not a very safe combination in general), and one affects a daemon that has daemon-excluded files that are being hidden in a module's hierarchy. Included are simple config-change suggestions that should help you to avoid the security issues. These

There are two security advisories for people who run a writable rsync daemon. One affects only those with "use chroot = no" (which is not a very safe combination in general), and one affects a daemon that has daemon-excluded files that are being hidden in a module's hierarchy. Included are simple config-change suggestions that should help you to avoid the security issues. These

Rsync version: rsync-2.5.6-3mdk (Mandrake 9.2) I see from the CVS log that some of the following awkwardness may be fixed (or at least different) in the next public release. I'm looking forward to that. In the interim, here are some problems: --------- Problem 1 - unexpected consequence of replacing / with ** --------- The following exclude works because the explicit slash causes a match

https://bugzilla.samba.org/show_bug.cgi?id=4764 Summary: Wrong include/exclude descriptions Product: rsync Version: 2.6.8 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: tps@vr-web.de QAContact:

I've released version 2.6.0 of rsync. Two important things to note in the new release: 1. The default remote shell is now "ssh" unless you tell the configure you want to use something else. 2. Some bug fixes in the include/exclude code, while making things work properly, have resulted in some user-visible changes for certain wildcard strings. Read the

https://bugzilla.samba.org/show_bug.cgi?id=13582 Bug ID: 13582 Summary: rsync filters containing multiple adjacent slashes aren't reduced to just one slash before matching Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5

This is version 4 of the following sub-series: [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() [libnbd PATCH v3 10/29] lib/utils: add unit tests for async-signal-safe execvpe() http://mid.mail-archive.com/20230215141158.2426855-10-lersek at redhat.com http://mid.mail-archive.com/20230215141158.2426855-11-lersek at redhat.com The Notes section on each patch records the

A thought has been nagging me for a bit now so i'll run it up the flagpole and see if anyone salutes. There seems to be quite a bit of confusion regarding the use of the leading slash as a top of tree anchor for exclude patterns. The manpage seems clear enough to me but somehow it doesn't seem to get through. What if we allowed a leading circumflex (^) to serve the same function. We

Hi, I am rsyncing from my source server A to a destination server B. A/vol1 contains two files syslog.txt and syslog.bak B/vol1 contains five files syslog.txt, syslog.bak, initlog.txt, internal.txt, and internal.bak. I want to preserve the 5 files on B/vol1 when I do rsync from A to B. Here is the command I use: rsync -av --delete --exclude-from=EXCLUDEFILE A/ B I've tried the option

Hi, I just noticed that the value of the '--compare-dest' argument is simply prepended to the DEST argument, even if that has path compnents. For example with this command: rsync -a --compare-dest=$comparedest \ remote::something/1/ \ /local/path/to/1/ if the remote 'something' module has a file called '1/2/3/4/file' (which is going to be mirrored to

hi, I am trying to rsync a very large filesystem which is about 3TB, but naturally I want to exclude a lot of things. However, I am really struggling with excluding directories. SRC=/dasd/december/2008 #Notice there is no trailing slash TARGET=/backup/december/2008 #Notice there is no trailing slash I want to exclude /dasd/december/2008/Data /dasd/december/2008/Logs

I just picked up rsync 2.5.6 and installed it. I haven't actually _used_ it for anything yet; this is entirely about a handful of minor issues I noticed while building it. You may care or you may not; for simplicity of language (to avoid many repeated "in case you care" and such), the text below is written assuming you care about them all. On a (32-bit) SPARC system, I noticed:

Except some of those dir have subdir such as WhatsApp and DCIM has multiple subdirs too. I would rather do it all with rsync though. On Wed, Sep 30, 2020, 12:54 PM Wayne Davison <wayne at opencoder.net> wrote: > On Tue, Sep 29, 2020 at 4:46 PM Rob Campbell wrote: > >> Thanks for your help. What you provided didn't work for me because that >> still placed things in

This bug may be specific to the portability releases of OpenSSH. It's minor, but trivially corrected. I'm observing it under: * openssh-2.3.0p1 (openssl-0.9.6) * compiled under Solaris 2.5.1 * running under Solaris 2.5.1 and Solaris 8 The relevant source code does not appear to have changed up to and including openssh-2.9p2. The bug is that the $MAIL environment variable

As of release samba-1.9.16p11, the X option (exclude file) for tar creates doesn't work recursively; if the exclude file is a directory, files that are in the directory or subdirectories are not excluded from the tar create. I would like the exclude feature to work recursively, and attached is a patch to do it. The exclude feature works the same way for both create and extracts. ***

Tom, There appears to be a broken link on the online manpage for shorewall.conf http://www.shorewall.net/manpages/shorewall.conf.html " *GEOIPDIR*=[/pathname/] Added in Shorewall 4.5.4. Specifies the pathname of the directory containing the /GeoIP Match/ database. See http://www.shorewall.net/ISOCODES.html. If not specified, the default value is

Hi all, I am having *massive* problems trying to exclude a single directory from an rsync. I have serv1 and serv2. I am trying to rsync /foo/test from serv1 to /foo on serv2 I want to exclude the directory /foo/test/dir1 So I try: rsync -av --exclude-from=/foo/rsync.excludes /foo/test serv2:/foo rsync.excludes contains: /foo/test/dir1/ This is not working. I also try: rsync -av

Hello, Since the very first day I've been using rsync - some 15 years ago - the filtering rules caused great grieve. Their behaviour is just not the way I'd expect it be be and as I read the manpage. Usually I end up with some hand-written recipes, carefully documented,y including all the gotchas. This time however I failed and I see no other way than to ask for advice. Given the