summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWayne Davison <wayned@samba.org>2014-03-07 14:27:18 -0800
committerWayne Davison <wayned@samba.org>2014-03-07 23:47:40 -0800
commit306d1127304f680d23d49847929725e549ded985 (patch)
treed7b37fb5346d02754ff35c96aba4391ba06b69bc
parent371242e4e8150d4f9cc74cdf2d75d8250535175e (diff)
downloadrsync-306d1127304f680d23d49847929725e549ded985.tar.gz
Mention how "max verbosity" affects info & debug opts.
-rw-r--r--rsync.yo8
-rw-r--r--rsyncd.conf.yo7
2 files changed, 15 insertions, 0 deletions
diff --git a/rsync.yo b/rsync.yo
index 6b558187..dfb541ab 100644
--- a/rsync.yo
+++ b/rsync.yo
@@ -513,6 +513,12 @@ fine-grained settings override the implied settings of bf(-v). Both
bf(--info) and bf(--debug) have a way to ask for help that tells you
exactly what flags are set for each increase in verbosity.
+However, do keep in mind that a daemon's "max verbosity" setting will limit how
+high of a level the various individual flags can be set on the daemon side.
+For instance, if the max is 2, then any info and/or debug flag that is set to
+a higher value than what would be set by bf(-vv) will be downgraded to the
+bf(-vv) level in the daemon's logging.
+
dit(bf(--info=FLAGS))
This option lets you have fine-grained control over the
information
@@ -534,6 +540,7 @@ information on what is output and when.
This option was added to 3.1.0, so an older rsync on the server side might
reject your attempts at fine-grained control (if one or more flags needed
to be send to the server and the server was too old to understand them).
+See also the "max verbosity" caveat above when dealing with a daemon.
dit(bf(--debug=FLAGS))
This option lets you have fine-grained control over the debug
@@ -554,6 +561,7 @@ specified, especially those pertaining to I/O and buffer debugging.
This option was added to 3.1.0, so an older rsync on the server side might
reject your attempts at fine-grained control (if one or more flags needed
to be send to the server and the server was too old to understand them).
+See also the "max verbosity" caveat above when dealing with a daemon.
dit(bf(--msgs2stderr)) This option changes rsync to send all its output
directly to stderr rather than to send messages to the client side via the
diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo
index 9e6a584d..3b7df513 100644
--- a/rsyncd.conf.yo
+++ b/rsyncd.conf.yo
@@ -318,6 +318,13 @@ the maximum amount of verbose information that you'll allow the daemon to
generate (since the information goes into the log file). The default is 1,
which allows the client to request one level of verbosity.
+This also affects the user's ability to request higher levels of bf(--info) and
+bf(--debug) logging. If the max value is 2, then no info and/or debug value
+that is higher than what would be set by bf(-vv) will be honored by the daemon
+in its logging. To see how high of a verbosity level you need to accept for a
+particular info/debug level, refer to "rsync --info=help" and "rsync --debug=help".
+For instance, it takes max-verbosity 4 to be able to output debug TIME2 and FLIST3.
+
dit(bf(lock file)) This parameter specifies the file to use to
support the "max connections" parameter. The rsync daemon uses record
locking on this file to ensure that the max connections limit is not