Kevin Korb (k...@sanitarium.net) wrote on 17 February 2014 21:13:
>OK, I just did a quickie test. When I 'ssh user@host rsync --daemon
>- --server .' an I don't have an rsyncd.conf file in my home dir I get
>no output like you do (an error message here would be nice). If I do
>have a proper r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I just did a quickie test. When I 'ssh user@host rsync --daemon
- --server .' an I don't have an rsyncd.conf file in my home dir I get
no output like you do (an error message here would be nice). If I do
have a proper rsyncd.conf file I get rsync
Kevin Korb (k...@sanitarium.net) wrote on 14 February 2014 12:51:
>Try running that ssh command line yourself and see what it says.
Doesn't say anything. But rsync is indeed run. I changed it to this
script:
#!/bin/bash
echo "run!"
echo "run!"
and
ural# rsync -avv -e "ssh -l root" ./orig/ ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try running that ssh command line yourself and see what it says.
On 02/14/2014 06:34 AM, Carlos Carvalho wrote:
> Kevin Korb (k...@sanitarium.net) wrote on 13 February 2014 21:47:
>> modules are defined in an rsyncd.conf file. That file needs to
>> b
On 14.02.2014 13:17, Paul Slootman wrote:
> On Fri 14 Feb 2014, Matthias Schniedermeyer wrote:
> >
> > You mixed the options from "remote shell" with "rsync daemon".
> > Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode.
>
> Matthias,
> Ik recommend you check out the "USING R
On Fri 14 Feb 2014, Matthias Schniedermeyer wrote:
>
> You mixed the options from "remote shell" with "rsync daemon".
> Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode.
Matthias,
Ik recommend you check out the "USING RSYNC-DAEMON FEATURES VIA A
REMOTE-SHELL CONNECTION" part
Matthias Schniedermeyer (m...@citd.de) wrote on 14 February 2014 13:06:
>You mixed the options from "remote shell" with "rsync daemon".
>Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode.
No, there's a third method. Search for
"USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL
On 13.02.2014 23:38, Carlos Carvalho wrote:
> I'm trying to transfer something to another machine launching a
> once-only "daemon" through ssh with this command:
>
> rsync -avv -e "ssh -l user" ./orig/ machine::module/
>
> where "module" is the name of a file in the home dir of user with the
> fo
Kevin Korb (k...@sanitarium.net) wrote on 13 February 2014 21:47:
>modules are defined in an rsyncd.conf file. That file needs to be in
>the home dir of the user.
You mean the config file must be called "rsyncd.conf" instead of "module"?
That'd be easy to solve but unfortunately it didn't work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
modules are defined in an rsyncd.conf file. That file needs to be in
the home dir of the user.
On 02/13/2014 08:38 PM, Carlos Carvalho wrote:
> I'm trying to transfer something to another machine launching a
> once-only "daemon" through ssh with thi
Le jeudi 15 novembre 2007, Maxim Veksler a écrit :
> Hello,
>
> I have 2 servers I'm synchronizing using rsync, I have a situation where I
> :
>
> 1. rsync from rnd-dev2 to rnd-dev1
> 2. change the rsynched file on rnd-dev1
> 3. rsync from rnd-dev2 to rnd-dev1 again
> 4. File gets overridden on rnd
bruary 22, 2007 10:34 AM
> To: rsync@lists.samba.org
> Subject: Re: Problem with Rsync or Users will be Users?
>
> Various web sites says this about NTFS files.
>
>
> Individual file names in NTFS are limited to 255 characters;
> full paths are limited to 32,767 character
> Path length limitiation comes from the underlying OS, cygwin in this
> case.
>
> It has a max path length of 260 chars, if I remember correctly.
Wow. That's quite a limitation.
I didn't realise.
Thanks Tevfik for that enlightenment. :-)
This email is the property of ECS Technology Ltd.
Thi
Various web sites says this about NTFS files.
Individual file names in NTFS are limited to 255 characters; full paths
are limited to 32,767 characters
This filename is a mere 191 long
Path is a lot less than 32,767... :-)
So how come it is an OS error when Rsync tries to copy it?
-
cluding the deep
> sections).
I think I know what you mean... :-)
Thank you for responding.
--
Stuart Halliday
-Original Message-
From: Wayne Davison <[EMAIL PROTECTED]>
To: Stuart Halliday <[EMAIL PROTECTED]>
Cc: rsync
Date: Wed, 21 Feb 2007 07:46:56 -0800
Subject:
On Wed, Feb 21, 2007 at 10:52:50AM +, Stuart Halliday wrote:
> rsync: mkstemp "..." failed: File name too long (91)
Note that this is an OS error, so rsync is just reporting the failure
that the mkstemp() call didn't work.
You might be able to work around the problem by copying more deeply in
On Wednesday, 24. May 2006, 09:07, Wayne Davison (as WD) wrote:
>WD: On Wed, May 24, 2006 at 07:56:54AM +0200, Andreas Fehr wrote:
>WD: > I'm back with my -cav and rsync does not copy files, even if I've
>WD: > touched them.
/opt/rsync/bin/rsync -cav
--link-dest=/home/user/backup/old
On Wed, May 24, 2006 at 07:56:54AM +0200, Andreas Fehr wrote:
> I'm back with my -cav and rsync does not copy files, even if I've
> touched them.
Are you copying into an already populated destination directory? It
sounds like it. When --link-dest is used to create a new hierarchy,
rsync will on
On Tuesday, 23. May 2006, 18:04, Andreas Fehr (as AF) wrote:
>AF: >WD: > Well, I changed '-a' to '-rlpgoD' (according to the man
>AF: >WD: > page, it maps to '-rlptgoD'). But now it's worse each
>AF: >WD: > call of rsync copies all the files from source to new.
>AF: >WD:
>AF: >WD: As Matt m
On Tuesday, 23. May 2006, 08:52, Wayne Davison (as WD) wrote:
>WD: On Tue, May 23, 2006 at 11:40:48AM +0200, Andreas Fehr wrote:
>WD: > Well, I changed '-a' to '-rlpgoD' (according to the man page, it
>WD: > maps to '-rlptgoD'). But now it's worse each call of rsync
>WD: > copies all the fil
On Tue, May 23, 2006 at 11:40:48AM +0200, Andreas Fehr wrote:
> Well, I changed '-a' to '-rlpgoD' (according to the man page, it maps
> to '-rlptgoD'). But now it's worse each call of rsync copies all
> the files from source to new.
As Matt mentioned, this was fixed recently in CVS. The fix c
On Tue, 2006-05-23 at 11:40 +0200, Andreas Fehr wrote:
> Well, I changed '-a' to '-rlpgoD' (according to the man page, it maps to
> '-rlptgoD'). But now it's worse each call of rsync copies all the
> files from source to new.
>
> /opt/rsync/bin/rsync -crlpgoDv
> --link-dest=/home/user/backup
On Tuesday, 23. May 2006, 11:07, Paul Slootman (as PS) wrote:
>PS: On Mon 22 May 2006, Andreas Fehr wrote:
>PS: >
>PS: > If added '-c' to the already existing '-a'. Now it looks as follows:
>PS: >
>PS: > /opt/rsync/bin/rsync -cav
>PS: > --link-dest=/home/user/backup/old
>PS: > /home/
On Mon 22 May 2006, Andreas Fehr wrote:
>
> If added '-c' to the already existing '-a'. Now it looks as follows:
>
> /opt/rsync/bin/rsync -cav
> --link-dest=/home/user/backup/old
> /home/user/source
> /home/user/backup/new
>
>
> I expected, that rsync doesn't care about
On Thursday 04 May 2006 13:11, Jordi de Groot wrote:
> Hi everyone,
>
>
>
>I'm using rsync in several Novell Servers, and some times I get this
> error:
>
>
>
> rsync: getaddrinfo: SSCC2NW 873: no address associated with hostname.
>
> rsync error: error in socket IO (code 10) at clientserver.c(
Re:
> > 1. from PC to HP-UX: rsh works, rsynch doesn't
>
> You should run rsync with -vv so you can see for sure what remote-shell
thanks...here's the result...
C:\rsync>type test.bat
@echo off
rsync -vv -auvzbPv test.bat ozma:/tmp/foo
C:\rsync>test
cmd= machine=ozma user= p
On Wed, Nov 09, 2005 at 02:50:37PM -0800, Stan Sieler wrote:
> rsync version 2.6.4 protocol version 29
> (2.6.6 requires too many things we don't have installed)
The only extra thing I see is the addition of a setlocale() call in
2.6.5, and you can just run "./configure --disable-locale" to avoi
Hi,
Can't help you much with the error but it seen to me you missing some thing:
> I map to a shared drive, then try and run rsync between the mail
directories of each machine
Rsync this way is actually copy the whole file each time (--whole-file)
To use rsync diff synchronize algorithm to
I have just figured out why my first compile of rsync wasn't working
correctly.
I had CFLAGS set to the following due to some "geeking off" with some custom
c programs I had been writting.
CFLAGS='-O9 -funroll-loops -ffast-math -malign-double -mcpu=pentiumpro -marc
h=pentiumpro -fomit-frame-point
I recompiled rsync on Machine A (the problem machine) and it has cleared up
the issue.
I am still trying to figure out what the issue was in the first place.
I have tried to duplicate the issue again, without any success.
Must have been a planitary alignment issue or coronal discharge while
comp
On Thu, Feb 06, 2003 at 04:10:57PM -0600, Justin Banks wrote:
> jw schultz wrote
> > Someone else has suggested using strace. Good idea but you need
> > to push (initiate the rsync on "A") for that to do much good.
>
> Actually, in the past I've replaced a remote service with a small program
> th
jw schultz wrote
> Someone else has suggested using strace. Good idea but you need
> to push (initiate the rsync on "A") for that to do much good.
Actually, in the past I've replaced a remote service with a small program
that executed strace /path/to/real/program, and had it work
just fine. I do
On Thu, Feb 06, 2003 at 03:01:07PM -0600, Tom Walsh wrote:
> I am not sure where to begin so I will be as verbose as I can to explain the
> problem.
>
> I have 3 servers. Their specs are:
>
> Machine A: Redhat 7.1 kernel 2.4.9-34 openssh 3.1p1-5
> Machine B: Redhat 7.3 kernel 2.4.9-31 openssh 3.1
Tom Walsh wrote
> Max,
>
> [root@magic /etc]# ls -la .pwd.lock
> -rw---1 root root0 Nov 29 2001 .pwd.lock
>
> Nothing special about that file... and like I said it occurs in any
> directory.
>
> If I do machineA.com:/etc/* (excluding files that start with .) it will hang
Tom Walsh wrote:
> [root@magic /etc]# ls -la .pwd.lock
> -rw---1 root root0 Nov 29 2001 .pwd.lock
>
> Nothing special about that file... and like I said it occurs in any
> directory.
>
> If I do machineA.com:/etc/* (excluding files that start with .) it
> will hang on DIR
::To: Tom Walsh; [EMAIL PROTECTED]
::Subject: Re: Problem with rsync from one machine
::
::
::Tom Walsh wrote:
::> rsync --verbose --progress --stats --compress --rsh=/usr/bin/"slogin
::> -l root -o Compression=yes" --recursive --times --links --perms
::> --owner --group m
Tom Walsh wrote:
> rsync --verbose --progress --stats --compress --rsh=/usr/bin/"slogin
> -l root -o Compression=yes" --recursive --times --links --perms
> --owner --group machineA.com:/etc /backup/machineA.com/etc
>
> The following occurs:
>
> All directories on Machine A /etc are replicated on
You should be able to find 3 rsync processes. 1 on the source box and 2 on
the destination.
Do a truss on the pid of the 'hung' processes and report back what state
they are in.
Also a netstat -na showing the Queues on the socket (port 22) might be
helpful.
What version of rysnc? What version of
If I understood everything correctly last time I read the ssh2 docs, I
believe that .shosts doesn't work with ssh2. I never got them to work
for myself, and it looks like your messages are complaining because
they're trying to find some form of input so they can give you a
password prompt.
What I
Hmm...I just started using rsync but my cron job commands look MUCH
different than yours. Did you create a public/private key (using
ssh-keygen2 -P) with no password and move it to both machines? You'll also
need to go into the /.ssh2 dir and create an authorization (public keys
authorized to co
40 matches
Mail list logo
