From owner-freebsd-bugs Wed Jul 25 20:20: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 26B7937B403 for ; Wed, 25 Jul 2001 20:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f6Q3K2686196; Wed, 25 Jul 2001 20:20:02 -0700 (PDT) (envelope-from gnats) Date: Wed, 25 Jul 2001 20:20:02 -0700 (PDT) Message-Id: <200107260320.f6Q3K2686196@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Barcroft Subject: Re: misc/14895: portmap bug (when run with -v flag) Reply-To: Mike Barcroft Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/14895; it has been noted by GNATS. From: Mike Barcroft To: David Lowe Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/14895: portmap bug (when run with -v flag) Date: Wed, 25 Jul 2001 23:35:31 -0400 On Mon, Jul 23, 2001 at 05:45:40PM -0700, David Lowe wrote: > Mike - > > I really don't have any machines more recent than 4.2-RELEASE to play with > at the moment. It's very predictable and easy to duplicate, if you have > access to such a machine. > > I am building a new machine within the next month or so, so I will test it > again once it's done if you are unable to do so. > > misc/12607 doesn't mention (in the fix) whether they explicitly ran > portmap with the -v flag in testing, nor does it explain *why* the bug > would go away under post-4.2. So I suspect that it's just that nobody has > tried it, but would be happy to be proven wrong. I don't have a 4.3-RELEASE or 4.3-STABLE box available for testing this, and 5.0-CURRENT seems to be using a new mechanism for RPC which doesn't exhibit this behaviour. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message