Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
liblongpath-rsync
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liblongpath
liblongpath-rsync
Commits
41ae04e0
Commit
41ae04e0
authored
Mar 27, 2010
by
Wayne Davison
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Get rid of trailing whitespace.
parent
9a7532e5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
14 deletions
+14
-14
rsync3.txt
rsync3.txt
+14
-14
No files found.
rsync3.txt
View file @
41ae04e0
-*- indented-text -*-
-*- indented-text -*-
Notes towards a new version of rsync
Notes towards a new version of rsync
Martin Pool <mbp@samba.org>, September 2001.
Martin Pool <mbp@samba.org>, September 2001.
...
@@ -51,7 +51,7 @@ Bad things about the current implementation:
...
@@ -51,7 +51,7 @@ Bad things about the current implementation:
hard to modify/extend
hard to modify/extend
- Both the program and the protocol assume a single non-interactive
- Both the program and the protocol assume a single non-interactive
one-way transfer
one-way transfer
- A list of all files are held in memory for the entire transfer,
- A list of all files are held in memory for the entire transfer,
which cripples scalability to large file trees
which cripples scalability to large file trees
...
@@ -88,7 +88,7 @@ Protocol philosophy:
...
@@ -88,7 +88,7 @@ Protocol philosophy:
Questionable features:
Questionable features:
These are neat, but not necessarily clean or worth preserving.
These are neat, but not necessarily clean or worth preserving.
- The remote rsync can be wrapped by some other program, such as in
- The remote rsync can be wrapped by some other program, such as in
tridge's rsync-mail scripts. The general feature of sending and
tridge's rsync-mail scripts. The general feature of sending and
...
@@ -100,7 +100,7 @@ Desirable features:
...
@@ -100,7 +100,7 @@ Desirable features:
These don't really require architectural changes; they're just
These don't really require architectural changes; they're just
something to keep in mind.
something to keep in mind.
- Synchronize ACLs and extended attributes
- Synchronize ACLs and extended attributes
- Anonymous servers should be efficient
- Anonymous servers should be efficient
...
@@ -122,7 +122,7 @@ Desirable features:
...
@@ -122,7 +122,7 @@ Desirable features:
Alternatively, as long as transfers are idempotent, we can just
Alternatively, as long as transfers are idempotent, we can just
restart the whole thing. [NFSv4]
restart the whole thing. [NFSv4]
- Scripting support.
- Scripting support.
- Propagate atimes and do not modify them. This is very ugly on
- Propagate atimes and do not modify them. This is very ugly on
Unix. It might be better to try to add O_NOATIME to kernels, and
Unix. It might be better to try to add O_NOATIME to kernels, and
...
@@ -224,7 +224,7 @@ Scripting hooks:
...
@@ -224,7 +224,7 @@ Scripting hooks:
- What basis file to use
- What basis file to use
- Logging
- Logging
- Whether to allow transfers (for public servers)
- Whether to allow transfers (for public servers)
- Authentication
- Authentication
...
@@ -275,7 +275,7 @@ Pie-in-the-sky features:
...
@@ -275,7 +275,7 @@ Pie-in-the-sky features:
These might have a severe impact on the protocol, and are not
These might have a severe impact on the protocol, and are not
clearly in our core requirements. It looks like in many of them
clearly in our core requirements. It looks like in many of them
having scripting hooks will allow us
having scripting hooks will allow us
- Transport over UDP multicast. The hard part is handling multiple
- Transport over UDP multicast. The hard part is handling multiple
destinations which have different basis files. We can look at
destinations which have different basis files. We can look at
...
@@ -344,7 +344,7 @@ In favour of using a new protocol:
...
@@ -344,7 +344,7 @@ In favour of using a new protocol:
- If we start from scratch, it can be documented as we go, and we
- If we start from scratch, it can be documented as we go, and we
can avoid design decisions that make the protocol complex or
can avoid design decisions that make the protocol complex or
implementation-bound.
implementation-bound.
Error handling:
Error handling:
...
@@ -365,7 +365,7 @@ Concurrency:
...
@@ -365,7 +365,7 @@ Concurrency:
- We can do nonblocking network IO, but not so for disk.
- We can do nonblocking network IO, but not so for disk.
- It makes sense to on the destination be generating signatures and
- It makes sense to on the destination be generating signatures and
applying patches at the same time.
applying patches at the same time.
- Can structure this with nonblocking, threads, separate processes,
- Can structure this with nonblocking, threads, separate processes,
etc.
etc.
...
@@ -381,7 +381,7 @@ Uses:
...
@@ -381,7 +381,7 @@ Uses:
http://www.ietf.org/proceedings/00jul/00july-133.htm#P24510_1276764
http://www.ietf.org/proceedings/00jul/00july-133.htm#P24510_1276764
- Sync with PDA
- Sync with PDA
- Network backup systems
- Network backup systems
- CVS filemover
- CVS filemover
...
@@ -419,7 +419,7 @@ Filesystem migration:
...
@@ -419,7 +419,7 @@ Filesystem migration:
Atomic updates:
Atomic updates:
The NFSv4 working group wants atomic migration. Most of the
The NFSv4 working group wants atomic migration. Most of the
responsibility for this lies on the NFS server or OS.
responsibility for this lies on the NFS server or OS.
If migrating a whole tree, then we could do a nearly-atomic rename
If migrating a whole tree, then we could do a nearly-atomic rename
at the end. This ties in to having separate basis and destination
at the end. This ties in to having separate basis and destination
...
@@ -427,11 +427,11 @@ Atomic updates:
...
@@ -427,11 +427,11 @@ Atomic updates:
There's no way in Unix to replace a whole set of files atomically.
There's no way in Unix to replace a whole set of files atomically.
However, if we get them all onto the destination machine and then do
However, if we get them all onto the destination machine and then do
the updates quickly it would greatly reduce the window.
the updates quickly it would greatly reduce the window.
Scalability:
Scalability:
We should aim to work well on machines in use in a year or two.
We should aim to work well on machines in use in a year or two.
That probably means transfers of many millions of files in one
That probably means transfers of many millions of files in one
batch, and gigabytes or terabytes of data.
batch, and gigabytes or terabytes of data.
...
@@ -466,4 +466,4 @@ Related work:
...
@@ -466,4 +466,4 @@ Related work:
- http://freshmeat.net/search/?site=Freshmeat&q=mirror§ion=projects
- http://freshmeat.net/search/?site=Freshmeat&q=mirror§ion=projects
- BitTorrent -- p2p mirroring
- BitTorrent -- p2p mirroring
http://bitconjurer.org/BitTorrent/
http://bitconjurer.org/BitTorrent/
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment