thr3ads.net
the human readable 3mail archive display system
rsync
-
Nov 2014
Search
rsync
10549 threads
Nov 2014
21 threads
Friday November 28 2014
Time
Replies
Subject
1:41AM
2
Bug-report:rsync may hung if time jumps backwards
Thursday November 27 2014
Time
Replies
Subject
8:05PM
0
Bug-report:rsync may hung if time jumps backwards
Wednesday November 26 2014
Time
Replies
Subject
10:43PM
0
rsync not transferring files [SOLVED]
Tuesday November 25 2014
Time
Replies
Subject
11:00PM
0
[Bug 10963] rsync to multiple destinations
10:58PM
6
[Bug 10963] New: rsync to multiple destinations
7:03PM
0
Dealing with an unreliable remote
4:27PM
0
Dealing with an unreliable remote
3:02PM
5
Dealing with an unreliable remote
Monday November 24 2014
Time
Replies
Subject
5:26AM
1
rsync not transferring files
Saturday November 22 2014
Time
Replies
Subject
8:12PM
1
rsync not transferring files
Friday November 21 2014
Time
Replies
Subject
7:46AM
4
[Bug 10951] New: Emtpy parameter triggers unwanted behavior, but no error message
Thursday November 20 2014
Time
Replies
Subject
5:59PM
1
[Bug 10950] New: rsync hangs when specifying a backup directory
Tuesday November 18 2014
Time
Replies
Subject
1:48AM
2
[Bug 10941] New: include should supersede max-size
Monday November 17 2014
Time
Replies
Subject
6:44AM
2
Bug-report:rsync may hung if time jumps backwards
Sunday November 16 2014
Time
Replies
Subject
9:53PM
1
Using --fuzzy
Saturday November 15 2014
Time
Replies
Subject
10:26AM
1
rsync stalls at .sparsebundle directories on OS X
Friday November 14 2014
Time
Replies
Subject
6:51AM
6
[Bug 10936] New: Rsync path hijacking attack vulnerability
Thursday November 13 2014
Time
Replies
Subject
5:26AM
1
rsync prevent destination only new folders but need new files
Friday November 7 2014
Time
Replies
Subject
1:38AM
4
[Bug 10925] New: non-atomic xattr replacement in btrfs => rsync --read-batch random errors
12:37AM
0
non-atomic xattr replacement in btrfs => rsync random errors
Sunday November 2 2014
Time
Replies
Subject
1:27PM
0
Rsync hangs on "No space left on device" on the server side