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
62b68c80
Commit
62b68c80
authored
Apr 08, 2002
by
Martin Pool
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Notes about logging.
parent
e4724e5c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
31 additions
and
25 deletions
+31
-25
TODO
TODO
+31
-25
No files found.
TODO
View file @
62b68c80
...
...
@@ -363,25 +363,6 @@ zlib
versions.
logging
Perhaps flush stdout after each filename, so that people trying to
monitor progress in a log file can do so more easily. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=48108
At the connections that just get a list of modules are not logged,
but they should be.
If a child of the rsync daemon dies with a signal, we should notice
that when we reap it and log a message.
Keep stderr and stdout properly separated (Debian #23626)
Use a separate function for reporting errors; prefix it with
"rsync:" or "rsync(remote)", or perhaps even "rsync(local
generator): ".
proxy authentication
Allow RSYNC_PROXY to be http://user:pass@proxy.foo:3128/, and do
...
...
@@ -572,15 +553,24 @@ Add machines
SCO
NICE -----------------------------------------------------------------
--no-detach and --no-fork options
LOGGING --------------------------------------------------------------
Very useful for debugging. Also good when running under a
daemon-monitoring process that tries to restart the service when th
e
parent exits.
Perhaps flush stdout after each filename, so that people trying to
monitor progress in a log file can do so more easily. Se
e
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=48108
hang/timeout friendliness
At the connections that just get a list of modules are not logged,
but they should be.
If a child of the rsync daemon dies with a signal, we should notice
that when we reap it and log a message.
Keep stderr and stdout properly separated (Debian #23626)
Use a separate function for reporting errors; prefix it with
"rsync:" or "rsync(remote)", or perhaps even "rsync(local
generator): ".
verbose output
...
...
@@ -589,6 +579,22 @@ verbose output
At end of transfer, show how many files were or were not transferred
correctly.
-vv
Explain *why* every file is transferred or not (e.g. "local mtime
123123 newer than 1283198")
NICE -----------------------------------------------------------------
--no-detach and --no-fork options
Very useful for debugging. Also good when running under a
daemon-monitoring process that tries to restart the service when the
parent exits.
hang/timeout friendliness
internationalization
...
...
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