search for: tools1

...ransfer time but is still active. It also ends by killing its calling process. The error looks different, though, but it's on a local nfs-to-nfs, instead of rsyncd-to-nfs. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ToolSyncProgress Replicating big1/cadappl1/hpux from chi-tools1 to chi-tools2 at 1004913115:2001:11:4:22:31:55. io timeout after 3600 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(75) ToolSyncProgress chinetsvr failed Replicating big1/cadappl1/hpux from /wan/chi-tools1/chi-tools1 to /wan/chi-tools2/chi-tools2 at 1004925444:200...

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server

...ink big1/cadappl1/hpux/ictools/tmpTempo: No such file or directory symlink big/tools/DI/factory_integrator2.2/data -> /cadappl/ictools/factory_integrator/2.2/data : File exists symlink big/tools/synopsys/synopsys1999.05/doc -> /cadappl/ictools/synopsys/1999.05/doc : File exists symlink big1/tools1/DI/dis2.2.2/DI/documentation -> /cadappl/ictools/Design_Integrator/2.2.2/documentation : File exists symlink big1/tools1/DI/dis2.2.2/DI/system -> /cadappl/ictools/Design_Integrator/2.2.2/system : File exists rsync error: partial transfer (code 23) at main.c(537) finished /bildmax/bildmax3 a...

...the list of modules as defined in your >rsyncd.conf (if you've restarted rsync --daemon after they were added) >with >rsync host:: >tconway@alta:/users/tconway/encap/build/SunOS/5.7/gnupg-1.0.6 > >rsync willy:: >big >big1 >ToolSyncModules >sjt-tools-master1 >sjt-tools1 >sjt-tools2 >Tools >tconway@alta:/users/tconway/encap/build/SunOS/5.7/gnupg-1.0.6 > >rsync willy::big1 >drwxr-xr-x 512 2002/04/09 10:33:58 . >drwxr-xr-x 512 2002/04/09 10:34:24 cadappl1 >drwxr-xr-x 512 2001/09/14 08:03:06 tools1 >tconway@alta:/users/t...

I use FreeBSD RELENG_4 with rsync version 2.5.4 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 32-bit system inums, 64-bit internal inums and when I try to transfer file I get rsync: connection unexpectedly closed (5994 bytes read so

This is my first post so first of all I will say hello to everyone. I have rsync configured and working properly on my local network however when I try to connect from a remote host (one located in a different state) the connection times out. I was wondering if there was another way to set the timeout besides in the rsyncd.conf file? As I said the connection works fine on the internal lan, but

Is it true that when running rsync via ssh (i.e. rsync -e ssh ...) the rsyncd.conf file is not applicable on the remote since rsync is launched via the ssh exec call once connected rather than from rsyncd as in a direct connect. If so, I am trying to find the best way to restrict rsync -e ssh on the remote machine. Prepending the authorized_keys entry with command='rsync ...' 1024...