From owner-freebsd-stable Mon Jul 19 12: 7:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fep8.mail.ozemail.net (fep8.mail.ozemail.net [203.2.192.102]) by hub.freebsd.org (Postfix) with ESMTP id 8A43C15273; Mon, 19 Jul 1999 12:07:15 -0700 (PDT) (envelope-from c9710216@atlas.newcastle.edu.au) Received: from atlas.newcastle.edu.au (slnew55p58.ozemail.com.au [203.108.151.136]) by fep8.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id FAA11466; Tue, 20 Jul 1999 05:06:57 +1000 (EST) Message-ID: <379376AB.1902B050@atlas.newcastle.edu.au> Date: Tue, 20 Jul 1999 05:04:11 +1000 From: obituary X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: "Chris D. Faulhaber" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Problem with cvsup References: <3793356A.EDC63408@atlas.newcastle.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > What version of CVSup do you run? If it's not 16.0, upgrade to 16.0, > or make sure you run cvsup with the '-P m' option (*not* '-m'; there > is no such option.) It's version 16.0. The -m I specified was an natd switch telling it to "try to keep the same port number when altering outgoing packets". I thought the default behaviour may have been confusing CVSup. > Do you run a clean kernel, or do you have any patches? There are SYN > rate limiting patches floating around which are known to badly break > the TCP/IP stack. No patches here. It's a clean 3.2-RELEASE kernel built from the distribution CD sources. -jake (obituary) Powered by FreeBSD c9710216@atlas.newcastle.edu.au http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message