From owner-freebsd-current Wed Feb 12 18:14:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA11665 for current-outgoing; Wed, 12 Feb 1997 18:14:06 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA11659 for ; Wed, 12 Feb 1997 18:14:01 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA01310; Wed, 12 Feb 1997 19:06:21 -0700 From: Terry Lambert Message-Id: <199702130206.TAA01310@phaeton.artisoft.com> Subject: Re: moused on notebooks... To: gurney_j@resnet.uoregon.edu Date: Wed, 12 Feb 1997 19:06:21 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: from "John-Mark Gurney" at Feb 12, 97 01:37:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > right now I'm running moused on my notebook w/ a ps/2 mouse... if I ever > have the mouse detacted when the notebook is up and running I will loose > the mouse until I restart moused... > > would anybody object to possibly added a signal handler to moused for > SIGHUP to force it to reopen the mouse device? comments? In the situation you describe, the SIGHUP would arive when you unplugged the mouse, not when you plugged it in. You want it to be opened *after* you plug it in. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.