From owner-freebsd-questions@freebsd.org Wed Apr 20 00:36:06 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6EAAB13454 for ; Wed, 20 Apr 2016 00:36:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A122810B5 for ; Wed, 20 Apr 2016 00:36:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3K0a54W010027 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Apr 2016 18:36:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3K0a5DI010024; Tue, 19 Apr 2016 18:36:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 19 Apr 2016 18:36:05 -0600 (MDT) From: Warren Block To: "Brandon J. Wandersee" cc: freebsd-questions@freebsd.org Subject: Re: Simple devd.conf rule has no effect In-Reply-To: Message-ID: References: <86fuuywldn.fsf@WorkBox.Home> <86bn552vga.fsf@WorkBox.Home> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 19 Apr 2016 18:36:05 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 00:36:06 -0000 Quick followup with an improvement: notify 20 { match "system" "ACPI"; match "subsystem" "Lid"; match "notify" "0x00"; action "/usr/bin/su wblock -c '/usr/local/bin/xlock -display :0.0 -mode qix &'"' action "acpiconf -s3"; }; It was backgrounding xlock that was important, not a delay after it started.