[Bug 13615] Output of --list-only not as I expected re: symlinks
https://bugzilla.samba.org/show_bug.cgi?id=13615 --- Comment #4 from Michael Hipp --- (In reply to Kevin Korb from comment #3) Thanks for the explanation. I would encourage someone to consider updating the documentation to be more like what you wrote - as what I get from reading the man page is nothing at all like that. > rsync --verbose --archive --itemize-changes --dry-run --ignore-times ./ > localhost:`pwd`/ Thanks for this. I will give it a try when I get back on that project. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 13615] Output of --list-only not as I expected re: symlinks
https://bugzilla.samba.org/show_bug.cgi?id=13615 --- Comment #3 from Kevin Korb --- I believe I talked to you in IRC about which is why I didn't respond when this was first posted but I think I can help explain this better... The --list-only option is to turn rsync into a network capable ls. It allows you to look around a remote filesystem that you can only access via rsync over ssh or rsyncd. It kinda implements some rsync options to kinda do more of what ls can do but it is still a bit of a kludge to allow you to look around. For local stuff using ls is a much better idea. That being said, if you want rsync output even if your target is unavailable you can always talk to localhost. You can do something like: rsync --verbose --archive --itemize-changes --dry-run --ignore-times ./ localhost:`pwd`/ The --ignore-times is there so rsync will think all files need to be copied and therefore they will always all be listed. Otherwise ./ and localhost:`pwd`/ will always be identical and nothing would be listed. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 13615] Output of --list-only not as I expected re: symlinks
https://bugzilla.samba.org/show_bug.cgi?id=13615 --- Comment #2 from Michael Hipp --- I'm sorry, I don't understand. The first line in the docs says: "This option will cause the source files to be listed instead of transferred." It doesn't say anything about "remote". It would seem to be a viable way to list the files that rsync will consider as candidates to transfer. It obeys the exclusions and such, why does it not obey such for its treatment of symlinks? Using --dry-run isn't really a substitute as it requires a connection to the remote server (destination) in the case of an ssh transfer. So it cannot be used if that remote server is not accessible. Is there any way to get a "correct" list of the files rsync will consider as candidates to transfer, but without making an unnecessary connection to the remote end? Thanks. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 13615] Output of --list-only not as I expected re: symlinks
https://bugzilla.samba.org/show_bug.cgi?id=13615 Wayne Davison changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Wayne Davison --- The --list-only option just tells rsync to do some remote file listings. You should use --dry-run if you want to know what a transfer is going to do. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 13615] New: Output of --list-only not as I expected re: symlinks
https://bugzilla.samba.org/show_bug.cgi?id=13615 Bug ID: 13615 Summary: Output of --list-only not as I expected re: symlinks Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: way...@samba.org Reporter: mich...@redmule.com QA Contact: rsync...@samba.org The output of --list-only isn't as I expected as regards symlinks. Here are my test files: $ ls ./src -rw--- 1 michael michael0 2018-09-05 09:18:15 file lrwxrwxrwx 1 michael michael4 2018-09-05 09:18:28 near_symlink -> file -rw--- 1 michael michael0 2018-09-13 12:39:41 exclude lrwxrwxrwx 1 michael michael4 2018-09-13 12:40:47 far_symlink -> /etc I want to know which files are candidates to transfer. I don't want symlinks to transfer. I run it with --list-only : $ rsync -r --no-links --list-only --exclude="/excl*" ./src/ drwx-- 4,096 2018/09/13 12:40:47 . lrwxrwxrwx 4 2018/09/13 12:40:47 far_symlink -rw--- 0 2018/09/05 09:18:15 file lrwxrwxrwx 4 2018/09/05 09:18:28 near_symlink This seems to indicate the symlinks are expected to transfer. Note that --list-only correctly handles exclusions. But when I actually run the transfer, the symlinks are not transferred: $ rsync -r --no-links --exclude="/excl*" ./src/ ./dest skipping non-regular file "far_symlink" skipping non-regular file "near_symlink" $ ls ./dest -rw--- 1 michael michael0 2018-09-13 12:49:06 file So it seems like --list-only is not being truthful as regards symlinks. Or else I misunderstand the purpose of --list-only. So I am submitting a request to either: a) correct the output of --list-only, or b) have the purpose and intended use case of --list-only be better explained in the docs. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Output of --list-only not as I expected for symlinks
Then that just leaves --dry-run. More flexibility you might not know: If you double --itemize-changes it will show all the files it considers including what it skips for being the same. If you double -v you will get debugging for include/exclude rules. On 09/12/2018 10:26 PM, Michael Hipp via rsync wrote: > My apologies. I'm evidently not communicating very well. > > I am not asking for a list of what "needs to be transferred", I am > looking for a list of those things that are "candidates to transfer". In > other words, the source items minus exclusions/filters or anything else > that will be ignored (by rsync). > > Is there any option for rsync that offers such a list? > >> find /path -type f -or -type d -print (or -ls) > > This tells me nothing about what *rsync* expects to do. In particular it > won't consider rsync's filters/exclusions. > > Thanks, > Michael > > On 2018-09-12 20:54, Kevin Korb via rsync wrote: >> How would it know what needs to be transferred without looking at both >> source and target? You are correct that it doesn't pay any attention to >> the target because it doesn't need a target. If the source is remote >> then it will connect to the remote to do a remote listing and if the >> source is local then no connection is needed but then neither is rsync. >> As far as obeying the recursive flag, so does ls. >> >> I didn't know it cared about exclude rules but you are right that it >> does. Guess I never tried. I only ever used it when I was trying to >> see what was on an rsync server. >> >> Anyway, if you want to list all the files and dirs but not symlinks and >> others in a local tree: >> find /path -type f -or -type d -print (or -ls) >> >> On 09/12/2018 07:53 PM, Michael Hipp via rsync wrote: >>> Thank you. But I'm afraid I don't understand. The man entry reads: >>> >>> "--list-only >>> This option will cause the source files to be listed instead of >>> transferred. This option is inferred if there is a single source arg and >>> no destination specified..." >>> >>> It doesn't say anything about "list remote files". In fact I am not sure >>> why it would even contact the remote end. And the behavior does not >>> change even if no destination is specified. >>> >>> As far as it ignoring the rest of the command line, note that it does >>> obey exclusion rules. Symlinks seem to be the only anomaly in its >>> output. >>> >>> I use --dry-run and --itemize-changes frequently. But I was trying to >>> find something that would give me a correct list of the candidate source >>> files but without having to make an expensive connect to the remote >>> server. Any suggestions? >>> >>> Thanks, >>> Michael Hipp >>> >>> >>> >>> On 2018-09-12 11:17, Kevin Korb via rsync wrote: --list-only is simply a way to list remote files when you only have access via rsync. It ignores the rest of the command line. You want --dry-run (--itemize-changes would be a good idea too). On 09/12/2018 11:06 AM, Michael Hipp via rsync wrote: > The output of --list-only isn't as I expected as regards symlinks. > Here > are my test files: > > $ ls ./src > -rw--- 1 michael michael 0 2018-09-05 09:18:15 file > lrwxrwxrwx 1 michael michael 4 2018-09-05 09:18:28 near_symlink > -> file > lrwxrwxrwx 1 michael michael 23 2018-09-05 09:19:05 far_symlink -> > /home/michael/Documents > > The "destination" dir is empty: > > $ ls ./dest > drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. > drwx-- 2 michael michael 4.0K 2018-09-12 09:50:20 . > > I want to know which files are candidates to transfer. I don't want > symlinks to transfer. So I run it with --list-only : > > $ rsync -r --no-links --list-only ./src/ ./dest > drwx-- 4,096 2018/09/06 09:39:16 . > lrwxrwxrwx 23 2018/09/05 09:19:05 far_symlink > -rw--- 0 2018/09/05 09:18:15 file > lrwxrwxrwx 4 2018/09/05 09:18:28 near_symlink > > This seems to indicate the symlinks are expected to transfer. But if I > actually run the transfer by removing --list-only ... > > $ rsync -r --no-links ./src/ ./dest > skipping non-regular file "far_symlink" > skipping non-regular file "near_symlink" > > It does not transfer the symlinks and this is confirmed by the > contents > of dest: > > $ ls ./dest > drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. > -rw--- 1 michael michael 0 2018-09-12 09:57:50 file > drwx-- 2 michael michael 4.0K 2018-09-12 09:57:50 . > > So it seems like --list-only isn't being truthful as it surely knows > beforehand the symlinks will not be transferred regardless of the > condition of dest. > > What am I missing? > > Thanks, > Michael Hipp > > >>> >>> >> >> > > --
Re: Output of --list-only not as I expected for symlinks
My apologies. I'm evidently not communicating very well. I am not asking for a list of what "needs to be transferred", I am looking for a list of those things that are "candidates to transfer". In other words, the source items minus exclusions/filters or anything else that will be ignored (by rsync). Is there any option for rsync that offers such a list? > find /path -type f -or -type d -print (or -ls) This tells me nothing about what *rsync* expects to do. In particular it won't consider rsync's filters/exclusions. Thanks, Michael On 2018-09-12 20:54, Kevin Korb via rsync wrote: How would it know what needs to be transferred without looking at both source and target? You are correct that it doesn't pay any attention to the target because it doesn't need a target. If the source is remote then it will connect to the remote to do a remote listing and if the source is local then no connection is needed but then neither is rsync. As far as obeying the recursive flag, so does ls. I didn't know it cared about exclude rules but you are right that it does. Guess I never tried. I only ever used it when I was trying to see what was on an rsync server. Anyway, if you want to list all the files and dirs but not symlinks and others in a local tree: find /path -type f -or -type d -print (or -ls) On 09/12/2018 07:53 PM, Michael Hipp via rsync wrote: Thank you. But I'm afraid I don't understand. The man entry reads: "--list-only This option will cause the source files to be listed instead of transferred. This option is inferred if there is a single source arg and no destination specified..." It doesn't say anything about "list remote files". In fact I am not sure why it would even contact the remote end. And the behavior does not change even if no destination is specified. As far as it ignoring the rest of the command line, note that it does obey exclusion rules. Symlinks seem to be the only anomaly in its output. I use --dry-run and --itemize-changes frequently. But I was trying to find something that would give me a correct list of the candidate source files but without having to make an expensive connect to the remote server. Any suggestions? Thanks, Michael Hipp On 2018-09-12 11:17, Kevin Korb via rsync wrote: --list-only is simply a way to list remote files when you only have access via rsync. It ignores the rest of the command line. You want --dry-run (--itemize-changes would be a good idea too). On 09/12/2018 11:06 AM, Michael Hipp via rsync wrote: The output of --list-only isn't as I expected as regards symlinks. Here are my test files: $ ls ./src -rw--- 1 michael michael 0 2018-09-05 09:18:15 file lrwxrwxrwx 1 michael michael 4 2018-09-05 09:18:28 near_symlink -> file lrwxrwxrwx 1 michael michael 23 2018-09-05 09:19:05 far_symlink -> /home/michael/Documents The "destination" dir is empty: $ ls ./dest drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. drwx-- 2 michael michael 4.0K 2018-09-12 09:50:20 . I want to know which files are candidates to transfer. I don't want symlinks to transfer. So I run it with --list-only : $ rsync -r --no-links --list-only ./src/ ./dest drwx-- 4,096 2018/09/06 09:39:16 . lrwxrwxrwx 23 2018/09/05 09:19:05 far_symlink -rw--- 0 2018/09/05 09:18:15 file lrwxrwxrwx 4 2018/09/05 09:18:28 near_symlink This seems to indicate the symlinks are expected to transfer. But if I actually run the transfer by removing --list-only ... $ rsync -r --no-links ./src/ ./dest skipping non-regular file "far_symlink" skipping non-regular file "near_symlink" It does not transfer the symlinks and this is confirmed by the contents of dest: $ ls ./dest drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. -rw--- 1 michael michael 0 2018-09-12 09:57:50 file drwx-- 2 michael michael 4.0K 2018-09-12 09:57:50 . So it seems like --list-only isn't being truthful as it surely knows beforehand the symlinks will not be transferred regardless of the condition of dest. What am I missing? Thanks, Michael Hipp -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Output of --list-only not as I expected for symlinks
How would it know what needs to be transferred without looking at both source and target? You are correct that it doesn't pay any attention to the target because it doesn't need a target. If the source is remote then it will connect to the remote to do a remote listing and if the source is local then no connection is needed but then neither is rsync. As far as obeying the recursive flag, so does ls. I didn't know it cared about exclude rules but you are right that it does. Guess I never tried. I only ever used it when I was trying to see what was on an rsync server. Anyway, if you want to list all the files and dirs but not symlinks and others in a local tree: find /path -type f -or -type d -print (or -ls) On 09/12/2018 07:53 PM, Michael Hipp via rsync wrote: > Thank you. But I'm afraid I don't understand. The man entry reads: > > "--list-only > This option will cause the source files to be listed instead of > transferred. This option is inferred if there is a single source arg and > no destination specified..." > > It doesn't say anything about "list remote files". In fact I am not sure > why it would even contact the remote end. And the behavior does not > change even if no destination is specified. > > As far as it ignoring the rest of the command line, note that it does > obey exclusion rules. Symlinks seem to be the only anomaly in its output. > > I use --dry-run and --itemize-changes frequently. But I was trying to > find something that would give me a correct list of the candidate source > files but without having to make an expensive connect to the remote > server. Any suggestions? > > Thanks, > Michael Hipp > > > > On 2018-09-12 11:17, Kevin Korb via rsync wrote: >> --list-only is simply a way to list remote files when you only have >> access via rsync. It ignores the rest of the command line. You want >> --dry-run (--itemize-changes would be a good idea too). >> >> On 09/12/2018 11:06 AM, Michael Hipp via rsync wrote: >>> The output of --list-only isn't as I expected as regards symlinks. Here >>> are my test files: >>> >>> $ ls ./src >>> -rw--- 1 michael michael 0 2018-09-05 09:18:15 file >>> lrwxrwxrwx 1 michael michael 4 2018-09-05 09:18:28 near_symlink >>> -> file >>> lrwxrwxrwx 1 michael michael 23 2018-09-05 09:19:05 far_symlink -> >>> /home/michael/Documents >>> >>> The "destination" dir is empty: >>> >>> $ ls ./dest >>> drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. >>> drwx-- 2 michael michael 4.0K 2018-09-12 09:50:20 . >>> >>> I want to know which files are candidates to transfer. I don't want >>> symlinks to transfer. So I run it with --list-only : >>> >>> $ rsync -r --no-links --list-only ./src/ ./dest >>> drwx-- 4,096 2018/09/06 09:39:16 . >>> lrwxrwxrwx 23 2018/09/05 09:19:05 far_symlink >>> -rw--- 0 2018/09/05 09:18:15 file >>> lrwxrwxrwx 4 2018/09/05 09:18:28 near_symlink >>> >>> This seems to indicate the symlinks are expected to transfer. But if I >>> actually run the transfer by removing --list-only ... >>> >>> $ rsync -r --no-links ./src/ ./dest >>> skipping non-regular file "far_symlink" >>> skipping non-regular file "near_symlink" >>> >>> It does not transfer the symlinks and this is confirmed by the contents >>> of dest: >>> >>> $ ls ./dest >>> drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. >>> -rw--- 1 michael michael 0 2018-09-12 09:57:50 file >>> drwx-- 2 michael michael 4.0K 2018-09-12 09:57:50 . >>> >>> So it seems like --list-only isn't being truthful as it surely knows >>> beforehand the symlinks will not be transferred regardless of the >>> condition of dest. >>> >>> What am I missing? >>> >>> Thanks, >>> Michael Hipp >>> >>> >> >> > > -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., signature.asc Description: OpenPGP digital signature -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Output of --list-only not as I expected for symlinks
Thank you. But I'm afraid I don't understand. The man entry reads: "--list-only This option will cause the source files to be listed instead of transferred. This option is inferred if there is a single source arg and no destination specified..." It doesn't say anything about "list remote files". In fact I am not sure why it would even contact the remote end. And the behavior does not change even if no destination is specified. As far as it ignoring the rest of the command line, note that it does obey exclusion rules. Symlinks seem to be the only anomaly in its output. I use --dry-run and --itemize-changes frequently. But I was trying to find something that would give me a correct list of the candidate source files but without having to make an expensive connect to the remote server. Any suggestions? Thanks, Michael Hipp On 2018-09-12 11:17, Kevin Korb via rsync wrote: --list-only is simply a way to list remote files when you only have access via rsync. It ignores the rest of the command line. You want --dry-run (--itemize-changes would be a good idea too). On 09/12/2018 11:06 AM, Michael Hipp via rsync wrote: The output of --list-only isn't as I expected as regards symlinks. Here are my test files: $ ls ./src -rw--- 1 michael michael 0 2018-09-05 09:18:15 file lrwxrwxrwx 1 michael michael 4 2018-09-05 09:18:28 near_symlink -> file lrwxrwxrwx 1 michael michael 23 2018-09-05 09:19:05 far_symlink -> /home/michael/Documents The "destination" dir is empty: $ ls ./dest drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. drwx-- 2 michael michael 4.0K 2018-09-12 09:50:20 . I want to know which files are candidates to transfer. I don't want symlinks to transfer. So I run it with --list-only : $ rsync -r --no-links --list-only ./src/ ./dest drwx-- 4,096 2018/09/06 09:39:16 . lrwxrwxrwx 23 2018/09/05 09:19:05 far_symlink -rw--- 0 2018/09/05 09:18:15 file lrwxrwxrwx 4 2018/09/05 09:18:28 near_symlink This seems to indicate the symlinks are expected to transfer. But if I actually run the transfer by removing --list-only ... $ rsync -r --no-links ./src/ ./dest skipping non-regular file "far_symlink" skipping non-regular file "near_symlink" It does not transfer the symlinks and this is confirmed by the contents of dest: $ ls ./dest drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. -rw--- 1 michael michael 0 2018-09-12 09:57:50 file drwx-- 2 michael michael 4.0K 2018-09-12 09:57:50 . So it seems like --list-only isn't being truthful as it surely knows beforehand the symlinks will not be transferred regardless of the condition of dest. What am I missing? Thanks, Michael Hipp -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Output of --list-only not as I expected for symlinks
--list-only is simply a way to list remote files when you only have access via rsync. It ignores the rest of the command line. You want --dry-run (--itemize-changes would be a good idea too). On 09/12/2018 11:06 AM, Michael Hipp via rsync wrote: > The output of --list-only isn't as I expected as regards symlinks. Here > are my test files: > > $ ls ./src > -rw--- 1 michael michael 0 2018-09-05 09:18:15 file > lrwxrwxrwx 1 michael michael 4 2018-09-05 09:18:28 near_symlink -> file > lrwxrwxrwx 1 michael michael 23 2018-09-05 09:19:05 far_symlink -> > /home/michael/Documents > > The "destination" dir is empty: > > $ ls ./dest > drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. > drwx-- 2 michael michael 4.0K 2018-09-12 09:50:20 . > > I want to know which files are candidates to transfer. I don't want > symlinks to transfer. So I run it with --list-only : > > $ rsync -r --no-links --list-only ./src/ ./dest > drwx-- 4,096 2018/09/06 09:39:16 . > lrwxrwxrwx 23 2018/09/05 09:19:05 far_symlink > -rw--- 0 2018/09/05 09:18:15 file > lrwxrwxrwx 4 2018/09/05 09:18:28 near_symlink > > This seems to indicate the symlinks are expected to transfer. But if I > actually run the transfer by removing --list-only ... > > $ rsync -r --no-links ./src/ ./dest > skipping non-regular file "far_symlink" > skipping non-regular file "near_symlink" > > It does not transfer the symlinks and this is confirmed by the contents > of dest: > > $ ls ./dest > drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. > -rw--- 1 michael michael 0 2018-09-12 09:57:50 file > drwx-- 2 michael michael 4.0K 2018-09-12 09:57:50 . > > So it seems like --list-only isn't being truthful as it surely knows > beforehand the symlinks will not be transferred regardless of the > condition of dest. > > What am I missing? > > Thanks, > Michael Hipp > > -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., signature.asc Description: OpenPGP digital signature -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Output of --list-only not as I expected for symlinks
The output of --list-only isn't as I expected as regards symlinks. Here are my test files: $ ls ./src -rw--- 1 michael michael0 2018-09-05 09:18:15 file lrwxrwxrwx 1 michael michael4 2018-09-05 09:18:28 near_symlink -> file lrwxrwxrwx 1 michael michael 23 2018-09-05 09:19:05 far_symlink -> /home/michael/Documents The "destination" dir is empty: $ ls ./dest drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. drwx-- 2 michael michael 4.0K 2018-09-12 09:50:20 . I want to know which files are candidates to transfer. I don't want symlinks to transfer. So I run it with --list-only : $ rsync -r --no-links --list-only ./src/ ./dest drwx-- 4,096 2018/09/06 09:39:16 . lrwxrwxrwx 23 2018/09/05 09:19:05 far_symlink -rw--- 0 2018/09/05 09:18:15 file lrwxrwxrwx 4 2018/09/05 09:18:28 near_symlink This seems to indicate the symlinks are expected to transfer. But if I actually run the transfer by removing --list-only ... $ rsync -r --no-links ./src/ ./dest skipping non-regular file "far_symlink" skipping non-regular file "near_symlink" It does not transfer the symlinks and this is confirmed by the contents of dest: $ ls ./dest drwxr-xr-x 31 michael michael 4.0K 2018-09-12 09:46:06 .. -rw--- 1 michael michael0 2018-09-12 09:57:50 file drwx-- 2 michael michael 4.0K 2018-09-12 09:57:50 . So it seems like --list-only isn't being truthful as it surely knows beforehand the symlinks will not be transferred regardless of the condition of dest. What am I missing? Thanks, Michael Hipp -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
