Matt McCutchen-7 wrote:
>
> On Tue, 2008-04-01 at 03:36 -0700, Peter Heiss wrote:
>>
>> Wayne Davison-2 wrote:
>> >
>> >
>> > Search for the string "admins" in the config file. You presumably set
>> > the gid in more than one spot, such as in the module's settings.
>> >
>>
>> I have check
On Tue, 2008-04-01 at 03:36 -0700, Peter Heiss wrote:
>
> Wayne Davison-2 wrote:
> >
> >
> > Search for the string "admins" in the config file. You presumably set
> > the gid in more than one spot, such as in the module's settings.
> >
>
> I have checked the config file and have not found any
Wayne Davison-2 wrote:
>
>
> Search for the string "admins" in the config file. You presumably set
> the gid in more than one spot, such as in the module's settings.
>
I have checked the config file and have not found any duplicates. Here is my
config file:
uid = user
gid = users
read only
On Wed, Mar 26, 2008 at 07:23:46AM -0700, Peter Heiss wrote:
> @ERROR: invalid gid admins
> I have "users" set as the gid in my rsync config file.
Search for the string "admins" in the config file. You presumably set
the gid in more than one spot, such as in the module's settings.
..wayne..
--
Matt McCutchen-7 wrote:
>
> I don't know, but here are a few things you can try. First, confirm
> that the daemon is accepting connections by running "nc localhost 873"
> on the remote machine. You should see the daemon's greeting, beginning
> with "@RSYNCD". Then, attempt to the daemon by ru
On Thu, 2008-03-20 at 07:04 -0700, Peter Heiss wrote:
> # rsync -zav --progress root@::realperson
> /random/file-or-directory
> rsync: failed to connect to : Connection timed out (110)
> rsync error: error in socket IO (code 10) at clientserver.c(104)
> [receiver=2.6.9]
>
> I have set up the daemo
On Thu 20 Mar 2008, Peter Heiss wrote:
> >> # rsync -zav --progress root@::realperson
> >> /random/file-or-directory
> >> rsync: failed to connect to : Connection timed out
> >> (110)
> >
> > A timeout would indicate a firewall problem, the rsync port (873) is
> > probably not allowed.
> >
>
>
> when I use the following command I dont get an error, I only get the
> timeout when i use the daemon to connect the remote server:
I don't use a daemon on the local pc to sync files with a remote server.
It's there only for responding to remote incoming rsync requests.
--
Stuart Halliday
Th
> I figured out the ssh error. Although I am still unable to connect to
> the
> remote host with the rsync daemon. Here is the error that I am getting
> again:
>
> # rsync -zav --progress root@::realperson
> /random/file-or-directory
> rsync: failed to connect to : Connection timed out
> (110)
>
Paul Slootman-5 wrote:
>
>> # rsync -zav --progress root@::realperson
>> /random/file-or-directory
>> rsync: failed to connect to : Connection timed out
>> (110)
>
> A timeout would indicate a firewall problem, the rsync port (873) is
> probably not allowed.
>
Yes I understand that ssh is not
On Thu 20 Mar 2008, Peter Heiss wrote:
>
> I figured out the ssh error. Although I am still unable to connect to the
> remote host with the rsync daemon. Here is the error that I am getting
> again:
To clarify: you know that ssh is now not involved, right?
> # rsync -zav --progress root@::realpe
I figured out the ssh error. Although I am still unable to connect to the
remote host with the rsync daemon. Here is the error that I am getting
again:
# rsync -zav --progress root@::realperson
/random/file-or-directory
rsync: failed to connect to : Connection timed out (110)
rsync error: error i
On Wed 19 Mar 2008, Peter Heiss wrote:
>
> Now I have a new situation, the linux OS was reinstalled (it crashed after a
> bad restart) on the remote linux box where I was working with rsync. I have
> reconfigured everything back to the way tit was before and I am now getting
> a new error with the
Now I have a new situation, the linux OS was reinstalled (it crashed after a
bad restart) on the remote linux box where I was working with rsync. I have
reconfigured everything back to the way tit was before and I am now getting
a new error with the following command:
# rsync -zav --progress :/ra
On Tue, 2008-03-18 at 03:38 -0700, Peter Heiss wrote:
> So now I have tried the daemon again, and got a password prompt, which is
> better. I edited the "host allow = *" so that it would allow all hosts. But
> I tried at first adding the IP Address of my local router, and it didnt
> work. How can I
Matt McCutchen-7 wrote:
>
>> hosts allow = trusted.hosts
>
> BTW, the "hosts allow" field needs to contain the actual list of trusted
> hosts, not the name of a file holding the list.
>
So now I have tried the daemon again, and got a password prompt, which is
better. I edited the "host allow
On Mon, 2008-03-17 at 05:58 -0700, Peter Heiss wrote:
> hosts allow = trusted.hosts
BTW, the "hosts allow" field needs to contain the actual list of trusted
hosts, not the name of a file holding the list.
Matt
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
On Mon, 2008-03-17 at 05:58 -0700, Peter Heiss wrote:
> Although, I am still having problems with
> the daemon on the remote server. I ran the command "rsync --daemon" on the
> remote server, no error there. But then I ran the following error to do a
> test backup and received this error:
>
> # rs
Matt McCutchen-7 wrote:
>
>>OK, let's be clear here. If you want to start a daemon to accept
>>connections, the command is "rsync --daemon"; pass a --config=FILE
>>option if you want to use a configuration file other than the
>>default /etc/rsyncd.conf . If you want to access an rsync daemon,
On Fri, 2008-03-14 at 14:15 +, Stuart Halliday wrote:
> Forget ssh until you've got it working as plain vanilla Rsync.
>
> Like I said in my 1st posting. Get a working daemon and then list a rsync
> folder using a Rsync list command.
>
> Don't do anything else until you've got that working.
>
I'd like to expand on Stuart's response a bit...
On Fri, 2008-03-14 at 06:29 -0700, Geofoxer wrote:
> Thanks for your response, I think that I am on my way of getting stuff
> configured here. I still have a couple of questions though. I am also using
> linux with rsync!!! I want to clear up the us
> Thanks for your response, I think that I am on my way of getting stuff
> configured here. I still have a couple of questions though. I am also
> using linux with rsync!!! I want to clear up the usage of the
> following command:
>
> rsync --progress -zav -e ssh /random/file-or-directory
> :/rand
Thanks for your response, I think that I am on my way of getting stuff
configured here. I still have a couple of questions though. I am also using
linux with rsync!!! I want to clear up the usage of the following command:
rsync --progress -zav -e ssh /random/file-or-directory
:/random/file-or-dir
Whilst it is possible to write a script to mount FTP and copy the files
across. This isn't what is usually done with Rsync.
Rsync can be a replacement for FTP client.
So it collects a list of altered files between two directories and puts
these files into a remote directory. No FTP required.
All
24 matches
Mail list logo
