From owner-freebsd-current Tue Aug 7 12:42:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B6DE37B417 for ; Tue, 7 Aug 2001 12:42:16 -0700 (PDT) (envelope-from mark@whistle.com) Received: from [207.76.207.129] (PBG4.whistle.com [207.76.207.129]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA41306; Tue, 7 Aug 2001 12:40:36 -0700 (PDT) Mime-Version: 1.0 X-Sender: mark-ml@207.76.206.1 Message-Id: In-Reply-To: <20010807151208.30cdcdb1.david@phobia.ms> References: <20010807151208.30cdcdb1.david@phobia.ms> Date: Tue, 7 Aug 2001 12:40:47 -0700 To: David Hill , freebsd-current@FreeBSD.ORG From: Mark Peek Subject: Re: kill -s does not work. Content-Type: text/plain; charset="us-ascii" ; format="flowed" 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 At 3:12 PM -0400 8/7/01, David Hill wrote: >While reading the exports(5) manpage, near the bottom is an example > >kill -s HUP `cat /var/run/mountd.pid` > >does kill -s causes this error: > ># 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). > >Does anyone have any comments? The short answer is, use "/bin/kill -s HUP `cat /var/run/mountd.pid`" for now. Here's the bug report and patch I submitted on this issue in June: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28109 It'll be fixed in the next release of tcsh. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message