rsyncd.conf should be installed as rsyncd.conf.example and /etc/init.d/rsyncd should check for the presense of /etc/rsyncd.conf before starting. this will prevent users from starting rsyncd with the default conf file. it will also allow custom ebuilds to install an /etc/rsyncd.conf file without having to worry about overwriting an existing file.
what exactly is wrong with starting rsyncd with default config file ? there is nothing in there that would cause problems as for installing .example, imo installing '.sample' or '.example' or whatever in /etc/ is garbage and all such packages should be shot :p i wouldnt mind installing into say /usr/share/rsync/ ... and why would custom rsync packages be allowed to install into /etc/rsyncd.conf but not rsync itself ? that seems a little wonky
Do I need to edit the /etc/rsyncd.conf or /etc/init.d/rsyncd? emerge net-misc/rsync (2.6.9) adds a config file to /etc/.
I'm surprised why the ebuild is now moving the rsyncd.conf from /etc/rsync/ to /etc. I thing /etc/rsync is a better location, where I can have another files like rsyncd.users and passwords ...
no reason for rsyncd.conf.example
