On 22 Mar 2002, Berend Tober <[EMAIL PROTECTED]> wrote:
> I noticed some mention somewhere about "reverse dns lookups" with
> respect to anonymous rsync, so what I did and got it to work, is add
> an entry to the /etc/hosts file on the server (192.168.123.4 in my
> example) for the back-up ser
On 21 Mar 02, at 19:40, Martin Pool wrote:
> On 21 Mar 2002, Berend Tober <[EMAIL PROTECTED]> wrote:
>
> >
> > hosts allow = 192.168.123.3
> > hosts deny = *.*.*.*
> >
>
> Try taking out the "hosts deny" line.
>
I noticed some mention somewhere about "reverse dns lookups" with
resp
> On 21 Mar 2002, Berend Tober <[EMAIL PROTECTED]> wrote:
>
> >
> > hosts allow = 192.168.123.3
> > hosts deny = *.*.*.*
> >
>
> Try taking out the "hosts deny" line.
>
> --
Am I reading the documentation wrong? What I read in the documentation, and
the way I've seen other implementation of allow
On 21 Mar 2002, Berend Tober <[EMAIL PROTECTED]> wrote:
> uid = nobody
> gid = nobody
> use chroot = yes
> read only=yes
> max connections = 2
> log file = /var/log/rsyncd.log
>
>
> hosts allow = 192.168.123.3
> hosts deny = *.*.*.*
>
> [ho
I'm trying to set up a back-up file server (192.168.123.3) that will
rsync files from the main production file server (192.168.123.4). The
production file server is set up to run rsync --daemon, and I know it
is doing so because on my backup server I can execute
rsync 192.168.123.4::
and get
Sounds like you want to do something like this:
http://killyridols.net/rsyncssh.shtml
-Dan Young
>I really want to use the anonymous rsync method so as to avoid having
>to type in the password manually, so that I can automate this with a
>cron script.
>
--
To unsubscribe or change options:
