Weirdness with --no-times option of rsync

2020-03-22 Thread T. Shandelman via rsync
Hi, rsync experts!

Would you please address the following issue (an apparent bug. But I would
rather reserve judgment and let you decide).

When rsync is run with the --no-times switch, file transfers based on time
difference indeed do not happen.

HOWEVER...
When -i (or -vv ?) is also specified, the transfer that does not happen is
nevertheless reported as if it *did *happen ( or under --dry-run, *would*
happen).

This issue is mentioned at :

https://askubuntu.com/questions/998491/rsync-ignore-times-parameter-not-working-on-ubuntu-16-04


  #  <<
  # Sorry, maybe I was not clear. I was referring to the 'T' tag under
transfer. If you
  # look for ' T ' (beware the two spaces) in the man page, it says: An
alternate value
  # of T means that the modification time will be set to the transfer
time, which happens
  # when a file/symlink/device is updated without --times and when a
symlink is changed
  # and the receiver can't set its time. (Note: when using an rsync
3.0.0 client, you
  # might see the s flag combined with t instead of the proper T flag
for this
  # time-setting failure) I was not able to make rsync to really ignore
times (no
  # reporting this). – Luis A. Florit Feb 21 '19 at 20:08
  #  >>


Thank you!
Todd Shandelman
Austin, Texas
-- 
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: Question/comment about -n (dry run) flag of rsync

2020-03-10 Thread T. Shandelman via rsync
No problem

On Tue, Mar 10, 2020, 18:05 raf via rsync  wrote:

> raf via rsync wrote:
>
> > T. Shandelman via rsync wrote:
> >
> > > Rsync is a remarkably handy tool that I use virtually every day.
> > >
> > > But there is one thing about rsync that drives me totally crazy.
> > >
> > > Under the -n (dry run) flag, rsync seems to produce exactly the same
> output
> > > as without that flag.
> > >
> > > I cannot tell you how many times I sit and scratch my head long and
> > > hard,after I discover that my intended rsync operations did not
> actually
> > > happen. Until I finally remember that I ran rsync in dry-run mode.
> That's
> > > why! This is especially a problem for very long-running rsync jobs run
> in
> > > dry-run mode.
> > >
> > > It seems to me that when run in dry-run mode, rsync should display a
> > > warning at the very, very end, something like:
> > >
> > > *WARNING: None of the above operations have been actually performed, *
> > > *because you ran rsync in dry-run mode.*
> > >
> > > Or does rsync already have such a feature, and I am not aware of it?
> > >
> > > But if not, that is my vote for the next feature to be added. It
> should be
> > > a very, very easy fix.
> > >
> > > Todd S.
> > > Austin, Texas, USA
> >
> > Bear in mind that it shouldn't happen by default as
> > that could break scripts that parse rsync's output. You
> > should need to request this behaviour in the config
> > file somehow.
>
> Oops. Please ignore that.
>
>
> --
> 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
>
-- 
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


Question/comment about -n (dry run) flag of rsync

2020-03-10 Thread T. Shandelman via rsync
Rsync is a remarkably handy tool that I use virtually every day.

But there is one thing about rsync that drives me totally crazy.

Under the -n (dry run) flag, rsync seems to produce exactly the same output
as without that flag.

I cannot tell you how many times I sit and scratch my head long and
hard,after I discover that my intended rsync operations did not actually
happen. Until I finally remember that I ran rsync in dry-run mode. That's
why! This is especially a problem for very long-running rsync jobs run in
dry-run mode.

It seems to me that when run in dry-run mode, rsync should display a
warning at the very, very end, something like:

*WARNING: None of the above operations have been actually performed, *
*because you ran rsync in dry-run mode.*


Or does rsync already have such a feature, and I am not aware of it?

But if not, that is my vote for the next feature to be added. It should be
a very, very easy fix.

Todd S.
Austin, Texas, USA
-- 
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