From owner-freebsd-current Tue Aug 7 12:28:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id E598037B410 for ; Tue, 7 Aug 2001 12:28:30 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.11.3/8.11.0) id f77JSP109679; Tue, 7 Aug 2001 12:28:25 -0700 (PDT) (envelope-from mph) Date: Tue, 7 Aug 2001 12:28:24 -0700 From: Matthew Hunt To: David Hill Cc: freebsd-current@FreeBSD.ORG Subject: Re: kill -s does not work. Message-ID: <20010807122824.A9612@wopr.caltech.edu> References: <20010807151208.30cdcdb1.david@phobia.ms> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010807151208.30cdcdb1.david@phobia.ms>; from david@phobia.ms on Tue, Aug 07, 2001 at 03:12:08PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Aug 07, 2001 at 03:12:08PM -0400, David Hill wrote: > # kill -s HUP > s: Unknown signal; kill -l lists signals. > > However, reading the kill(1) manpage, -s is documented. > So, I am thinking this is a bug in kill(1). I bet you are using csh, and running the kill builtin instead of kill(1). -- Matthew Hunt * Clearly there are more things in the http://www.pobox.com/~mph/ * heavens than anyone anticipated. -enp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message