From owner-freebsd-questions Wed Jan 13 11:07:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02681 for freebsd-questions-outgoing; Wed, 13 Jan 1999 11:07:54 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02663 for ; Wed, 13 Jan 1999 11:07:49 -0800 (PST) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.8/8.8.8) id JAA08351; Wed, 13 Jan 1999 09:17:38 -0600 (CST) Date: Wed, 13 Jan 1999 09:17:38 -0600 (CST) From: Mark Tinguely Message-Id: <199901131517.JAA08351@plains.NoDak.edu> To: droberts@gwis.com Subject: Re: rdump fails between freebsd machines Cc: freebsd-questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG we used to rdump between FreeBSD 2.2.7 machines all the time. I say `used to' because we have upgraded to newer versions of FreeBSD a while back. 2.2.7-RELEASE shipped with a bad /usr/libexec/rshd. I assume that since you can do rsh and rdumps from other platforms, you upgraded this daemon. is there any messages on the tape machine's /var/log/messages? for example failing "rmt" programs. since rsh of the same data seems to work, you would think it would not be the tape drive, but for giggles, have you tried to see if sending the data to the tape machine's /dev/null (or to a file on the tape machine if you have a large enough filesystem) also does not work? I would also watch the dump process with tcpdump maybe that can shed some more clues on to what is happening on the network. --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message