From owner-freebsd-questions@FreeBSD.ORG Sat Feb 17 22:19:21 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 95BEF16A406 for ; Sat, 17 Feb 2007 22:19:21 +0000 (UTC) (envelope-from lists@lrnx.ath.cx) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id 59B7813C4A6 for ; Sat, 17 Feb 2007 22:19:21 +0000 (UTC) (envelope-from lists@lrnx.ath.cx) Received: from hermes.lrnx.net (fr141-1-82-237-217-212.fbx.proxad.net [82.237.217.212]) by smtp5-g19.free.fr (Postfix) with ESMTP id 1F41A27985; Sat, 17 Feb 2007 23:19:20 +0100 (CET) Received: from [192.168.1.19] (zstar.blois.fr.lrnx.local [192.168.1.19]) by hermes.lrnx.net (8.13.6/8.13.6) with ESMTP id l1HMJJmN054213; Sat, 17 Feb 2007 23:19:19 +0100 (CET) (envelope-from lists@lrnx.ath.cx) Message-ID: <45D77F61.5080409@lrnx.ath.cx> Date: Sat, 17 Feb 2007 23:19:13 +0100 From: Pierre-Francois LAURAND User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <45D74B17.7050305@lrnx.ath.cx> <200702171504.57146.kirk@strauser.com> In-Reply-To: <200702171504.57146.kirk@strauser.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hermes.lrnx.net [82.237.217.212]); Sat, 17 Feb 2007 23:19:19 +0100 (CET) X-Virus-Scanned: ClamAV 0.90/2591/Sat Feb 17 20:29:32 2007 on astra.blois.fr.lrnx.local X-Virus-Status: Clean Cc: Subject: Re: Why this script does not work as expected ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2007 22:19:21 -0000 Kirk Strauser a écrit : > On Saturday 17 February 2007 12:36, Pierre-Francois LAURAND wrote: > >> /usr/bin/time /usr/bin/nice -n 20 /sbin/dump -C 16 -0 -f- /vol1 | \ >> /usr/bin/nc -v s-backup 24864 > > Try the "-a" option to dump, which tells it to output until it receives a > write error. Otherwise, it tries to chop up the dumps into tape-sized pieces > (even when writing to stdout), and the default tape size seems to be tiny. dump does not seem to be involved : On client : backup@client:/tmp$ if (/usr/bin/ssh -c blowfish backup@s-backup \ /usr/bin/nc -lv 24864 \>/tmp/file.1m &); then \ /bin/dd if=/dev/random bs=512k count=2 | \ /usr/bin/nc -v s-backup 24864; fi On remote, I only have a 1024 bytes file size: backup@s-backup:/tmp$ ls -l -rw-r----- 1 backup operator - 1024 17 feb 22:52 file.1m But, if on s-backup : backup@s-backup:/tmp$ /usr/bin/nc -lv 24864 | /bin/dd of=/tmp/file.1m And on client : backup@client: dd if=/dev/random bs=512k count=2 | \ /usr/bin/nc -v s-backup 24864 I get the expected result on s-backup: backup@s-backup:/tmp$ ls -l -rw-r----- 1 backup operator - 1048576 17 feb 22:54 file.1m So, I think that ssh is the one that break the transmission. -- pf