2016-01-11 21:32 GMT+01:00 Les Mikesell <lesmikes...@gmail.com>: > I don't recognize that 'unknown host' log entry. If the transfers > wait for whatever is writing it, it might cause a delay where the time > will depend on the DNS response - if you get an immediate NXDOMAIN > from a local server it should be quick but if you are referred to an > upstream and possibly firewalled server that won't respond you would > have a multiple-second wait for a timeout.
dns resolution is done just on connect, not for each file. So, the delay would be just for the first connection attempt, after that, speed is normal as no dns resolution is made. And, as wrote multiple times, the same server with standard rsync is working perfect. Only BPC is having trouble. > You could test the theory with "nslookup 172.17.0.1" to see how long > the response takes if that is the actual address. $ time nslookup 172.17.0.1 Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find 1.0.17.172.in-addr.arpa: NXDOMAIN real 0m0.108s user 0m0.004s sys 0m0.004s is fast enough for you? DNS is not an issue here. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
