rsyncd dies during data transfer
Hi All, I am running rsync on bsdi/os 4.2 where one machine is running it as a server and the other is accessing it. it's just to copy user directories and mails. The command I am using is simple in format i.e. rsync -avz source destination::list but sometimes during transfer it just dies out and my log files shows the following errors: 2001/04/25 16:50:56 [686] rsync to user from host.domain.com 2001/04/25 17:08:36 [686] transfer interrupted (code 20) at rsync.c(229) 2001/04/25 17:08:36 [687] transfer interrupted (code 20) at main.c(663) oh by the way I am using rsync rsync version 2.4.6 protocol version 24 Can someone please help me with this. Regards, Faisal __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Re: feature-request: libwrap
Dave Dykstra [EMAIL PROTECTED] writes: What are the advantages of that over rsyncd.conf's hosts allow and hosts deny? The main advantage would be the ability for sites that already use tcpwrappers to centralize their network authorization mechanism. Having this information spread out in lots of little separate files is harder to maintain than keeping it all under one framework in one set of configuration files. That being said, it is possible to hide rsync daemons behind tcpwrappers tcpd, it is just less efficient than having it be built in to the server itself (and you still have two sets of config files to contend with). Respectfully, David N. Blank-Edelman
Re: feature-request: libwrap
--On Wednesday, April 25, 2001 3:06 PM -0400 David N. Blank-Edelman [EMAIL PROTECTED] wrote: Dave Dykstra [EMAIL PROTECTED] writes: What are the advantages of that over rsyncd.conf's hosts allow and hosts deny? The main advantage would be the ability for sites that already use tcpwrappers to centralize their network authorization mechanism. Having this information spread out in lots of little separate files is harder to maintain than keeping it all under one framework in one set of configuration files. That being said, it is possible to hide rsync daemons behind tcpwrappers tcpd, it is just less efficient than having it be built in to the server itself (and you still have two sets of config files to contend with). Respectfully, David N. Blank-Edelman I agree with this... In fact, it isn't even difficult to add tcpwrappers support to rsync... What would it be? A few lines of code? I think the most difficulty is adding support to the configuration process of the applications that want to use it... but heck, you can rip that code out of something else that does that too :-) In any the case, it is cleaner to add support directly within the application, since it covers all the bases (inetd vs standalone), runs more efficiently (less forking) and adds another useful feature to your list (tcpwrappers support!) ;-) Just another penny to add to the well... Scott -- +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ Scott W. Adkinshttp://www.cns.ohiou.edu/~sadkins/ UNIX Systems Engineer mailto:[EMAIL PROTECTED] ICQ 7626282 Work (740)593-9478 Fax (740)593-1944 +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ CNS, HDL Center, Suite 301, Ohio University, Athens, OH 45701-2979
Re: delete a single file?
On Wed, Apr 25, 2001 at 12:06:07PM +0200, andreas haupt wrote: Hello all, a quick one possibly: can I use rsync to delete a single file remotely? Assume I have deleted a file locally and I want it removed remotely but without having to rsync the whole directory. rsync --delete file remote_machine:. does not work but gives me a 'link_stat' error because the file does not exist anymore locally. (I know how to use rsh remote_machine rm file . The question is: can rsync do this?) for those ever curious about the background: I'm syncing big sites once per week but might be forced occasionally to delete singular files before the big rsync takes place. Using rsync to do this would save me time. You can't use rsync itself, but the remote target to rsh can be a quoted shell command that runs before the rsync copy and then sends the target name to stdout: rsync source remote_machine:'`rm file;echo targetdir`' - Dave Dykstra
Re: feature-request: libwrap
On Wed, Apr 25, 2001 at 03:20:58PM -0400, Scott Adkins wrote: --On Wednesday, April 25, 2001 3:06 PM -0400 David N. Blank-Edelman [EMAIL PROTECTED] wrote: Dave Dykstra [EMAIL PROTECTED] writes: What are the advantages of that over rsyncd.conf's hosts allow and hosts deny? The main advantage would be the ability for sites that already use tcpwrappers to centralize their network authorization mechanism. Having this information spread out in lots of little separate files is harder to maintain than keeping it all under one framework in one set of configuration files. That being said, it is possible to hide rsync daemons behind tcpwrappers tcpd, it is just less efficient than having it be built in to the server itself (and you still have two sets of config files to contend with). Respectfully, David N. Blank-Edelman I agree with this... In fact, it isn't even difficult to add tcpwrappers support to rsync... What would it be? A few lines of code? I think the most difficulty is adding support to the configuration process of the applications that want to use it... but heck, you can rip that code out of something else that does that too :-) In any the case, it is cleaner to add support directly within the application, since it covers all the bases (inetd vs standalone), runs more efficiently (less forking) and adds another useful feature to your list (tcpwrappers support!) ;-) Just another penny to add to the well... That's a good reason, and I would think that if somebody submitted a good quality patch to support libwrap it would be accepted. - Dave Dykstra
Re: rsync newbie problem
On Wed, 25 Apr 2001, Bob Foster wrote: Hello, I'm trying to set up an rsync that will run without operator intervention. I have the daemon running on the receiving server and here is the module: [test] path = /web/test comment = test uid = siteadm gid = web read only = no list = yes auth users = siteadm secrets file = /etc/rsyncd.scrt hosts allow = 10.154.33.21 127.0.0.0/8 I use this script put_rsync on the sending server: /usr/local/bin/rsync -auv --delete --password-file=/dir/.rsync_pw /web/test/$1 [EMAIL PROTECTED]::test This works great if I am sending a directory such as /web/test/dir1 with the command ./put_rsync dir1 However, if I try to send /web/test/dir1/images with the command ./put_rsync images/dir1 it rsyncs to /web/test/images on the receiving server instead of /web/test/dir1/images What am I missing? try putting a slash at the end of images phma
