From owner-cvs-all  Wed Aug 26 14:00:19 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA17404
          for cvs-all-outgoing; Wed, 26 Aug 1998 14:00:19 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17308;
          Wed, 26 Aug 1998 14:00:09 -0700 (PDT)
          (envelope-from dillon@FreeBSD.org)
From: Matt Dillon <dillon@FreeBSD.ORG>
Received: (from dillon@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id OAA06770;
	Wed, 26 Aug 1998 14:00:04 -0700 (PDT)
Date: Wed, 26 Aug 1998 14:00:04 -0700 (PDT)
Message-Id: <199808262100.OAA06770@freefall.freebsd.org>
To: "Dag-Erling C. Sm\xf8rgrav" <des@FreeBSD.ORG>
Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: Re: cvs commit: src/sbin/ping ping.c
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

:
:des         1998/08/26 11:51:37 PDT
:
:  Modified files:
:    sbin/ping            ping.c 
:  Log:
:  Remove -c restrictions from previous commit.
:  
:  Revision  Changes    Path
:  1.41      +1 -13     src/sbin/ping/ping.c

    Sounds good.    I do think that the -f restrictions should be
    left in as well as the -i restrictions (only root can ping < 1 second
    interval).  -s restrictions could also be removed or a limit could
    be set for non-root users.

    The problems we've had with an unlimited -c has been more one of 
    forgetfullness... a user will start a ping going and forget to kill
    it.  It would be nice if ping did *NOT* default to an 'infinite' count,
    even if users are allowed to specify an option to set an infinite count.

					-Matt