Re: [PATCH] Consider nanoseconds when quick-checking for unchanged files

2016-01-20 Thread Paul Slootman
On Wed 20 Jan 2016, Wayne Davison wrote: > equal. One possible improvement would be to skip the nanosecond check if > the destination file has a nanosecond value of 0. That could possibly be > improved if we figure out if a particular device ID supports nanoseconds > somehow. I have a potential

[Bug 11683] New: hang on select when send many files

2016-01-20 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=11683 Bug ID: 11683 Summary: hang on select when send many files Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priori

Re: [PATCH] Consider nanoseconds when quick-checking for unchanged files

2016-01-20 Thread Wayne Davison
On Thu, Dec 25, 2014 at 2:48 AM, Ingo Brückl wrote: > On systems using nanoseconds differences should be taken into > consideration. > The problem is that if you transfer from a filesystem that has nanoseconds to one that does not support it, rsync would consider most of the files to be constant

Re: [PATCH] Consider nanoseconds when quick-checking for unchanged files

2016-01-20 Thread Andrey Gursky
On Wed, 20 Jan 2016 16:17:57 +0100 Paul Slootman wrote: > On Wed 20 Jan 2016, Andrey Gursky wrote: > > > > I was just about to implement the same, since nanoseconds are taken > > into account when transferring, thus making it obvious not to ignore > > Really? I thought the protocol only transmi

Re: [PATCH] Consider nanoseconds when quick-checking for unchanged files

2016-01-20 Thread Paul Slootman
On Wed 20 Jan 2016, Andrey Gursky wrote: > > I was just about to implement the same, since nanoseconds are taken > into account when transferring, thus making it obvious not to ignore Really? I thought the protocol only transmits seconds. Paul -- Please use reply-all for most replies to avoid

Re: [PATCH] Consider nanoseconds when quick-checking for unchanged files

2016-01-20 Thread Andrey Gursky
On Wed, 20 Jan 2016 12:58:51 +0100 Ingo Brückl wrote: > I wrote on Fri, 02 Jan 2015 16:02:27 +0100: > > > --- a/generator.c 2014-06-14 01:05:08.0 +0200 > > +++ b/generator.c 2015-01-02 15:50:30.0 +0100 > > @@ -588,7 +588,14 @@ > > if (ignore_times) > >

Re: [PATCH] Consider nanoseconds when quick-checking for unchanged files

2016-01-20 Thread Ingo Brückl
I wrote on Fri, 02 Jan 2015 16:02:27 +0100: > --- a/generator.c 2014-06-14 01:05:08.0 +0200 > +++ b/generator.c 2015-01-02 15:50:30.0 +0100 > @@ -588,7 +588,14 @@ > if (ignore_times) > return 0; > - return cmp_time(st->st_mtime, file->modt

Re: rsync stopped working

2016-01-20 Thread Bob Holtzman
On Wed, Jan 20, 2016 at 05:38:51PM +0900, SATOH Fumiyasu wrote: > Hi, > > At Wed, 20 Jan 2016 01:11:58 -0700, > Bob Holtzman wrote: > > Running Debian 8.2, xfce 4.10, rsync 3.1.1-3. I just edited my backup > > script as follows: > > Your backup script is broken. You've got me confused. The scr

Re: rsync stopped working

2016-01-20 Thread Joe
I'm not a whiz at this, but a couple of things look odd. 1) Your exclude file is *probably* in /home/holtzm - not in /holtzm 2) I don't think your source should be /. (although it might be right - but it looks like rsync doesn't like it). I think that /. ought to be the same as / . Usually i

Re: rsync stopped working

2016-01-20 Thread SATOH Fumiyasu
Hi, At Wed, 20 Jan 2016 01:11:58 -0700, Bob Holtzman wrote: > Running Debian 8.2, xfce 4.10, rsync 3.1.1-3. I just edited my backup script > as follows: Your backup script is broken. > #The first line deletes extraneous files. The second does not and is used for > normal backups. > > # rsync

rsync stopped working

2016-01-20 Thread Bob Holtzman
Running Debian 8.2, xfce 4.10, rsync 3.1.1-3. I just edited my backup script as follows: #The first line deletes extraneous files. The second does not and is used for normal backups. # rsync -vaHz --delete --exclude '/proc' --exclude '*.iso' --exclude '/sys' --exclude '/home/holtzm/Documents/*