From owner-freebsd-current Mon Oct 19 07:39:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11413 for freebsd-current-outgoing; Mon, 19 Oct 1998 07:39:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11398 for ; Mon, 19 Oct 1998 07:38:54 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id KAA27305; Mon, 19 Oct 1998 10:38:18 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08396; Mon, 19 Oct 1998 10:38:18 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA23348; Mon, 19 Oct 1998 10:38:18 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199810191438.KAA23348@bb01f39.unx.sas.com> Subject: Re: Conflicting ping performance In-Reply-To: <199810191423.HAA03011@implode.root.com> from David Greenman at "Oct 19, 98 07:23:46 am" To: dg@root.com Date: Mon, 19 Oct 1998 10:38:18 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Are you telling me it 'should' work this way now? Or that this behaviour is a bug and was introduced in 1.40? It would appear that the -i option is adversely affecting the -f option, and, yes, I am running this test as root so -c should allow infinity. If it's a bug, I'll look into a submitting a diff... Thanks, John > > We're seeing some very interesting ping timings. Wall-clock vs. > >recorded ping statistics. > > > > In the statistics below, the -current system is recording ping > >statistics 1/2 the values of the march snap. However, the march > >snap completes in 0.05 seconds, while the -current system requires > >10 seconds. A system running the 980825-SNAP gives the same strange > >results as the -current system. > > > > The network controllers should not have any effect since we are > >testing against localhost. (however, the two machines below are > >identical hardware configs using fxp0). > > > > This problem replicates when testing the actual network devices. > > > > Can anyone else replicate this problem? > > > > Comments, Critiques, or diffs to fix this are appreciated. > > Caused by this: > > RCS file: /home/ncvs/src/sbin/ping/ping.c,v > ... > ---------------------------- > revision 1.41 > date: 1998/08/26 18:51:37; author: des; state: Exp; lines: +1 -13 > Remove -c restrictions from previous commit. > ---------------------------- > revision 1.40 > date: 1998/08/26 01:58:39; author: dillon; state: Exp; lines: +38 -11 > (well tested at BEST): -i option can now take FP values (e.g. -i 0.1), > extremely useful for networking testing. Other options secured from > user-level D.O.S. attacks. -f, -s now root-only. -i wait times < 1.0 > root-only. -c count limited to 100 and defaults to 16 when ping run > by non-root user. > > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message