rsync - Mar 2004 - Rsync doesn't log properly when in standalone daemon mode

I'm trying to get over an exasperating problem with rsync 2.5.7, but
I'm not making any headway.  The nut of the problem is that the
rsync daemon seemingly ignores the "syslog facility" configuration
when running in standalone daemon mode, as opposed to being started
with inetd.

So, for example, if I have my configuration file with

	[global]
		pid file	= /etc/rsync/rsyncd.pid
		lock file	= /etc/rsync/rsyncd.lock
		use chroot	= true
		max connections	= 1
		hosts deny	= 0.0.0.0/0
		read only	= true
		list		= false
		uid		= nobody
		gid		= nobody
		secrets file	= /etc/rsync/secrets
		ignore errors	= true
		transfer logging= false
		syslog facility	= uucp
	#	log file	= /tmp/rsyncd.log
		timeout		= 30

	[archive]
	... blah blah blah ...

I get log entries in the uucp log files when running out of inetd.  But
running as a standalone daemon with the same config file, log entries
get dumped into the default syslog facility: daemon.

I've tried fiddling with file permissions on the configuration file and
these configuration variables,

	use chroot = false
	transfer logging = true
	syslog facility =  different facilities

and even logging to a file, but it still logs to the daemon syslog.  Is there
some subtlety I'm missing here?  Any light shed here would be appreciated.
Othwerwise I guess I patch the source.

On another tangential topic, why does logging on the server get controlled
by the client?  I'd like to have the client determine the verboseness of
their rsync output without having it also filling up server log files with
useless details.

Joseph Tam <tam@math.ubc.ca>

On Fri, Mar 26, 2004 at 01:17:27AM -0800, Joseph Tam
wrote:
> 	[global]
> 		transfer logging= false
> 		syslog facility	= uucp
If you get rid of the [global] heading and just put those items at the
start of the file, it should work:

[...]
transfer logging= false
syslog facility	= uucp
[...]

Your config file was specifying a module named "global", and those
settings didn't affect other modules.
> On another tangential topic, why does logging on the server get controlled
> by the client?  I'd like to have the client determine the verboseness
of
> their rsync output without having it also filling up server log files with
> useless details.
Improving this is on the list of future enhancements/fixes.  The current
code caps the user-supplied verboseness at 1 (so you can't get -vvvv
amounts of logging at the user's whim), but it would be better to have
the server-side logging totally under the control of the config file.

..wayne..