From owner-cvs-all  Sun Dec  9 12:18:39 2001
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id BE78437B405; Sun,  9 Dec 2001 12:18:36 -0800 (PST)
Received: (from iedowse@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id fB9KIa251331;
	Sun, 9 Dec 2001 12:18:36 -0800 (PST)
	(envelope-from iedowse)
Message-Id: <200112092018.fB9KIa251331@freefall.freebsd.org>
From: Ian Dowse <iedowse@FreeBSD.org>
Date: Sun, 9 Dec 2001 12:18:36 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/usr.sbin/rpc.umntall rpc.umntall.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

iedowse     2001/12/09 12:18:36 PST

  Modified files:
    usr.sbin/rpc.umntall rpc.umntall.c 
  Log:
  Don't ignore SIGINT and SIGQUIT. The comment said "Ignore SIGINT
  and SIGQUIT during shutdown", but rpc.umntall is also run at boot
  time, so ignoring these signals is a really bad idea: it makes it
  impossible to ^C the process as it waits for a server response. I
  can't see any reason to block these signals during shutdown either.
  
  MFC after:      3 days
  
  Revision  Changes    Path
  1.9       +1 -5      src/usr.sbin/rpc.umntall/rpc.umntall.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message