From owner-freebsd-bugs  Sat Dec 20 03:08:14 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA07929
          for bugs-outgoing; Sat, 20 Dec 1997 03:08:14 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA07914;
          Sat, 20 Dec 1997 03:08:04 -0800 (PST)
          (envelope-from joerg@FreeBSD.org)
From: Joerg Wunsch <joerg@FreeBSD.ORG>
Received: (from joerg@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id DAA08194;
	Sat, 20 Dec 1997 03:04:55 -0800 (PST)
Date: Sat, 20 Dec 1997 03:04:55 -0800 (PST)
Message-Id: <199712201104.DAA08194@freefall.freebsd.org>
To: imdave@mcs.net, joerg@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/5322
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Synopsis: enhancement for kill(1) to search for a file ``/var/run/*pid''

State-Changed-From-To: open-closed
State-Changed-By: joerg
State-Changed-When: Sat Dec 20 12:02:13 MET 1997
State-Changed-Why: 

The functionality to kill something by process name is already covered
by killall(1).  The functionality to signal some process by PID file
seems useful, too, but IMHO should not be crunched into kill(1).  A
simple shell script would do way better here (what about `signal' for
a name?).