On Thu 14 Jul 2005, [EMAIL PROTECTED] wrote:
[repositories]
comment = Subversion Repositories
path = /usr/local/repositories
read only = no
list = yes
hosts allow = 127.0.0.1
auth users = username
secrets file = /etc/rsyncd.secrets
However running rsync [EMAIL
Hi,
On Thu, 14 Jul 2005 [EMAIL PROTECTED] wrote:
I'm trying to set up an rsync daemon on my OS X machine to sync my
remote subversion repositories. My config file /etc/rsyncd.conf looks
like this:
motd file = /etc/motd
max connections = 25
syslog facility = local3
[repositories]
comment =
On Thu, Jul 14, 2005 at 12:00:54AM +, [EMAIL PROTECTED] wrote:
@ERROR: access denied to repositories from localhost (::1)
Did you check the log file to see what the daemon had to say about the
failure? Perhaps the permissions are wrong on your secrets file (which
would cause rsync to ignore
Hi Hardy:
Thanks for your comments. They are greatly appreciated.
I tried your suggestion regarding the UID and GID. I set them to
the owner and group of the /bak directory. Also I currently have
the permissions on the directory at 777. I killed and restarted
the server process and retried
Hugh, I did a quick test with 2.5.5, and here's what made it
work for me - the 'read only' parameter. Here's my daemon
/etc/rsyncd.conf file:
log file = /var/log/rsync
# this is a comment
[rsync-test]
uid=test
gid=test
read only=no
path=/test_rsync
it didn't work
Hi Hardy:
Nice catch - I missed that one when I reviewed the man page.
Unfortunately it made no difference. I have also tried moving
the module params from the global section to the module section
but that also made no difference - exactly same messages.
Just to keep things straight, here is my
On Fri, Jul 04, 2003 at 12:17:43PM -0700, Hugh E Cruickshank wrote:
hosts allow = fisdev pgiprd
Each of these names needs to be either a fully-qualified hostname, a
wildcard expression that matches a fully-qualified hostname, an IP
address, localhost, or some combination thereof. E.g.:
hosts
Ok, I think I've got it narrowed down.
1) First, comment out both 'hosts allow' and 'auth users',
save it, kill and restart the rsync daemon, and try your
rsync again. Hopefully that will work.
2) Uncomment the 'hosts allow' line, save, kill and
restart daemon, and try rsync again - you will
On Mon, Jul 07, 2003 at 03:38:15PM -0400, Hardy Merrill wrote:
[...] kill and restart the rsync daemon, and try your rsync again.
I've noticed that it's not necessary to kill and restart the rsync
daemon to get it to honor changes to the rsyncd.conf file. FYI.
..wayne..
--
To unsubscribe or
Hi Wayne:
You are correct. This did make a difference but did not resolve the
problem. See my previous response to Hardy Merrill's message.
Thanks, Hugh
--
Hugh E Cruickshank, Forward Software, www.forward-software.com
From: Wayne Davison Sent: Monday, July 07, 2003 12:36
On Fri, Jul 04,
Hi Wayne:
That's good to know. I thought that it might be the case (as it is
with SAMBA), but I did not see anything obvious in the man pages
(that or I am blind - always a good possibility).
Regards, Hugh
From: Wayne Davison Sent: Monday, July 07, 2003 12:44
On Mon, Jul 07, 2003 at
If anyone else has any ideas, please chime in, as I'm
getting to the end of my list of things to try. The
server is a SCO box and the client is a RH8 box.
Hugh, let's go back to the beginning - in your first
message, you stated:
---
In the above example fisdev is an SCO
Hi Hardy:
I had originally setup 2 rsync servers one on SCO OSR5 (fisdev, our
development server) and one on RH8 (pgiprd, our production server).
During my initial tests I tried using both fisdev as the server with
pgiprd as the client as well as pgiprd as the server with fisdev as
the client.
On Mon, Jul 07, 2003 at 02:38:02PM -0700, Hugh E Cruickshank wrote:
Hi Wayne:
That's good to know. I thought that it might be the case (as it is
with SAMBA), but I did not see anything obvious in the man pages
(that or I am blind - always a good possibility).
It is documented in the
Yes, the man page clearly states:
Note that you should not send the rsync server a HUP sig-
nal to force it to reread the /etc/rsyncd.conf. The file
is re-read on each client connection.
So I am obviously blind or at least not as attentive as I should be.
Hugh, I'm fairly new to rsync myself, so hopefully other
rsync gurus can either confirm or correct my thoughts here.
My comments are below.
Hugh E Cruickshank [EMAIL PROTECTED] wrote:
Hi All:
I am new to rsync so be gentle with me. I have been able to get
Me too :)
rsync working enough to
16 matches
Mail list logo
