transfer interrupted (code 3) at flist.c(812)

[tim.conway at philips.com]

try using a forward slash instead of a backslash.  that might do it... 
also, if it's cygwin, try /cygdrive/c/whatever.

Tim Conway
tim.conway at philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), 
".\n" '
"There are some who call me.... Tim?"




"Kapoor, Nishikant X" <Nishikant.X.Kapoor at xcelenergy.com>
Sent by: rsync-admin at lists.samba.org
11/16/2001 09:36 AM

 
        To:     rsync at lists.samba.org
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        transfer interrupted (code 3) at flist.c(812)
        Classification: 



Ok, I just setup the log file and this is what I see there:

rsync on cdrive/Temp/pix.log from admx (141.214.137.139)
transfer interrupted (code 3) at flist.c(812)

I had to change [cdrive] from path = "c:\" to path = c: to get rid of
'@ERROR: chdir failed' error.

I am getting close but still need some help. Thanks in advance.
Nishi

> -----Original Message-----
                 From:           Kapoor, Nishikant X
[SMTP:Nishikant.X.Kapoor at xcelenergy.com]
> Thanks for the help. I did go through quite a few docs but could not
> figure that out. Thanks again.
> 
> However, after setting [cdrive], I am getting the following error:
> 
> admx::nkapoor> rsync -v guest at testor::cdrive/Temp/pix.log .
> 
> @ERROR: chdir failed
> read error: Connection reset by peer
> 
> Is there a log file that I could use to see what exaclty is going on ?
> Or a debug level that could be set to see the trail ?
> 
> Thanks
> Nishi
> 
> > -----Original Message-----
> > From:                tim.conway at philips.com 
[SMTP:tim.conway at philips.com]
> > 
> > You'll have to chose between the external transport via ssh and the
> > rsync daemon.  The commandline to use the rsyncd, based on your
> > example, would be 
> > rsync -v guest at testor::"c:/Temp/pix.log" . 
> > I'm guessing, however, that you don't have a module named "c:" in
> your
> > rsyncd.conf. 
> > I would hope that if you're trying to use the rsyncd, you have
> > something like 
> > +++++++++++++++++++++++++++ 
> > [cdrive] 
> > path = "c:\" 
> > +++++++++++++++++++++++++++ 
> > in your rsyncd.conf.  that would mean your commandline would be 
> > rsync -v guest at testor::cdrive/Temp/pix.log . 
> > 
> > the internal transport (rsyncd connection) is signified by the
> double
> > colon "::" delimiter between the host and the path, which in this
> case
> > is the name of the module, followed by the path to the subdirectory.
> 
> > the single colon means to open a tcp connection to the remote
> machine,
> > execute "rsync --server
> > --whateverotherundocumentedoptionsitusesinthiscircumstance", and use
> > that as the remote.  the "-e ssh" means to use ssh instead of the
> > default rsh. 
> > 
> > Tim Conway
> > tim.conway at philips.com
> > 
> >              "Kapoor, Nishikant X" <Nishikant.X.Kapoor at xcelenergy.com> 

> > 
> > Here is a newbie question. Hope, you will not mind.
> > 
> > I am trying to backup a file from my NT machine onto AIX machine.
> Here
> > is the setup:
> > 
> > NT machine (testor): rsync is in c:\Rsync\rsync.exe and is running
> as
> > a
> > daemon. (I created a service for Rsync first).
> > 
> > AIX machine (admx): rsync -v
> > rsync version 2.3.1 Copyright Andrew Tridgell and Paul Mackerras
> > admx::nkapoor> telnet testor 873
> > Trying...
> > Connected to testor.
> > Escape character is '^]'.
> > @RSYNCD: 24
> > 
> > So, the rsync daemon seems fine on testor but the problem occurs
> when
> > I
> > try this:
> > 
> > admx::nkapoor> rsync -v -e ssh --rsync-path=c:/rsync/rsync.exe
> > guest at testor:"c:/Temp/pix.log" . 
> > Secure connection to testor refused.
> > unexpected EOF in read_timeout
> > 
> > I have checked that 'guest' is a valid user on testor. Could someone
> > please help me understand what could be the problem here ?
> > 
> > Thanks
> > Nishi
> 




-------------- next part --------------
HTML attachment scrubbed and removed