From owner-freebsd-stable Sun Aug 29 18:49: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 9700B14C1B for ; Sun, 29 Aug 1999 18:49:01 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id LAA02894; Mon, 30 Aug 1999 11:46:56 +1000 (EST) Received: from lightning.itga.com.au(192.168.71.20) via SMTP by fw.bby.com.au, id smtpd002892; Mon Aug 30 01:46:51 1999 Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id LAA29906; Mon, 30 Aug 1999 11:46:51 +1000 (EST) Message-Id: <199908300146.LAA29906@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: "Jeffrey J. Libman" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: dump to remote system aborting In-reply-to: Your message of Sat, 28 Aug 1999 22:28:44 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Aug 1999 11:46:51 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > DUMP: dumping (Pass IV) [regular files] > DUMP: master/slave protocol botched. > DUMP: The ENTIRE dump is aborted. If the .bashrc/.cshrc/. file for the tape user (usually root) on the remote (tape) host prints anything to stdout, then this error will occur. A typical culprit is an stty command that works fine for login, but puts out a "not a tty" error message when used from rsh. You can check this by running something like "rsh tapehost -l remuser ls /" from the dump host and seeing if anything unusual happens. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message