From owner-freebsd-questions Tue Apr 8 14:30:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA03255 for questions-outgoing; Tue, 8 Apr 1997 14:30:57 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA03250 for ; Tue, 8 Apr 1997 14:30:53 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id OAA01460; Tue, 8 Apr 1997 14:30:43 -0700 (PDT) Date: Tue, 8 Apr 1997 14:30:43 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Charles Owens cc: questions list FreeBSD Subject: Re: dump produces setsockopt error. Why? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Apr 1997, Charles Owens wrote: > Hi, > > Sometimes, but not always, when using dump to do a backup between to > FreeBSD boxes I get the error > > itsdsv3.enc.edu: Connection refused > TCP_MAXSEG setsockopt: Bad file descriptor > > (itsdsv3 is the remote host, of course) > > Any ideas as to what's causing this? Both hosts are running 2.1-stable > (just slightly pre-2.1.5-RELEASE... yes, I know, I need to upgrade). You need to tell itsdsv3 to accept rsh connections. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major