From owner-freebsd-stable  Mon Sep 20 17:28:27 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 779AF151C7
	for <freebsd-stable@FreeBSD.ORG>; Mon, 20 Sep 1999 17:28:19 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40384>; Tue, 21 Sep 1999 10:25:48 +1000
Date: Tue, 21 Sep 1999 10:27:40 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: Does rdump write the backup to an ordinary file?
In-reply-to: <5212.937871144@localhost>
To: freebsd-stable@FreeBSD.ORG
Message-Id: <99Sep21.102548est.40384@border.alcanet.com.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Jordan K. Hubbard" <jkh@zippy.cdrom.com> wrote:
>> Yes; on the destination machine, do a "touch /tmp/var.dump" to create the
>> file before running the backup.
>
>Really?  I never knew that worked. :)

It's sort-of documented in rmt(8):
BUGS
     People should be discouraged from using this for a remote file access
     protocol.

There are a few caveats:
1) It uses rexec/rcmd, which is a security hole.
2) The destination file won't be truncated by rmt or rdump.  This means
   that if you dump 5GB (say) into it one day and 1GB (say) the next,
   the file will still report as 5GB.

Peter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message