Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • --include="*/" --include-from=/tmp/mover-include.list that seems contradictory? Commented Oct 21 at 11:55
  • Not at all, the first --include="*/" is mandatory to include root folders Commented Oct 21 at 11:56
  • my rsync filter rules are a bit rusty, but why would you need to do that (you would need to do that for each lower directory containing one of the files) – you only want the files from the list, right? wouldn't -R solve that elegantly? Commented Oct 21 at 11:59
  • I didn't try it. Possibly, but that certainly doesn't answer my question. And I don't really see the relevance of the -R (which tells rsync to use relative paths) Commented Oct 21 at 12:05
  • 1
    hm, the point is that we don't have access to your full list, nor to your actual file set. Chances of rsync bugs are really far from zero, but in this case my bet is the old adage that "software does exactly what it's told to; that's what makes it so harmful" applies: It simply seems fileb simply does not get included for some reason. So, simplifying your rsync command line to isolate exactly what leads to that file not being included is not only an exercise in elegance, it's a necessity to be able to reproduce or understand the problem, and in the end, solve it :) Commented Oct 21 at 12:48