From owner-freebsd-hackers Tue Mar 26 03:01:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA27120 for hackers-outgoing; Tue, 26 Mar 1996 03:01:23 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA27109 for ; Tue, 26 Mar 1996 03:01:16 -0800 (PST) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id NAA26924; Tue, 26 Mar 1996 13:03:41 +0200 Date: Tue, 26 Mar 1996 13:03:40 +0200 (EET) From: Narvi To: David Greenman cc: Bill Fenner , Brian Tao , FREEBSD-HACKERS-L Subject: Re: Restricting ping -s and -l In-Reply-To: <199603260455.UAA07756@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Eat good food, preserve nature, be nice to all nice people :) On Mon, 25 Mar 1996, David Greenman wrote: > >Speaking of ping, anyone mind if I modify ping to print out ICMP errors that > >it receives in response to the ICMP_ECHO messages that it's sending out? It > >has always bothered me that you have to use "ping -v" to diagnose things like > >getting ICMP unreachables. > > Yes, I'd like to see this, too. "ping -v" is far too verbose on a busy > machine...when all I'm interested in is my own stuff. How about a special flag to tell it not to be *so verbose*? Something like ping -vb (following pkzip) or something like that. It would keep it more compatible with existing scripts which happen to use the output of ping. Sander (hoping not to have rewrite his scripts) > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project >