xinetd is the daemon. It will
spawn rsync processes as connections come to 872 (assuming that's the port
you associated with whatever you named that service). This is assuming,
of course, that xinetd has read the configuration since you made the change,
either by HUP, xinetd bounce, or system b
On Tue, Dec 07, 2004 at 10:06:26AM +0100, Paul Slootman wrote:
> You connect to the rsync daemon by using a command line like:
> rsync -avz 192.168.10.1::qmail-control .
> Of course, you will have to have started the daemon on 192.168.10.1
I am not able to get it running properly.
# ps aux|grep r
> Hi,
> This is the first time I have setup rsync.conf like,
>
> max connections = 20
> syslog facility = local3
> read only = true
> hosts allow = 192.168.10.10
> [qmail-control]
> comment = qmail-control
> path = /var/qmail/control
> read only = yes
> list = yes
>
On Mon 06 Dec 2004, Payal Rathod wrote:
> This is the first time I have setup rsync.conf like,
[...]
> Then from 192.168.10.10, I tried,
> rsync -avz -e ssh [EMAIL PROTECTED]:/var/qmail/control/* .
> and it worked. So far so good. But then again it worked from 192.168.10.11
Rsyncd.conf is only u
Hi,
This is the first time I have setup rsync.conf like,
max connections = 20
syslog facility = local3
read only = true
hosts allow = 192.168.10.10
[qmail-control]
comment = qmail-control
path = /var/qmail/control
read only = yes
list = yes
uid = root