From owner-freebsd-rc@FreeBSD.ORG Wed Apr 14 21:33:46 2010 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7044E1065672 for ; Wed, 14 Apr 2010 21:33:46 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 30A6E8FC0A for ; Wed, 14 Apr 2010 21:33:45 +0000 (UTC) Received: from mobileKamikaze.norad (unknown [109.250.180.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 2D91B8A1AD1; Wed, 14 Apr 2010 23:06:24 +0200 (CEST) Message-ID: <4BC62E4C.2060700@bsdforen.de> Date: Wed, 14 Apr 2010 23:06:20 +0200 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-GB; rv:1.9.1.9) Gecko/20100331 Thunderbird/3.0.4 MIME-Version: 1.0 To: Doug Barton References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-rc@FreeBSD.org Subject: Re: Trivial PR, fix shutdown of rc services started with onestart (fwd) X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2010 21:33:46 -0000 On 14/04/2010 22:18, Doug Barton wrote: > This issue has come up several times in the past, and previously I've > been opposed to making changes since I don't regard typing "onestop" an > overwhelming burden. :) However there is a reasonable argument to be > made for having things work when the system is shut down. Think of this like a laptop user. You've got to leave quickly, so you press the power button. 10 minutes later you power back on and want to log back into VPN. Darn, you forgot to log out and now you've got to wait for for another 20 minutes, before your old session times out and you're permitted back in. There's a good reason stop_cmds normally do more than 'kill $pid'. And the results of not executing them can be much more dire than having to wait for a 30 minutes time out to complete (if you've deal with fuse, severe data loss can be the result). Also, do you keep track of what you stared if your laptop is running for a couple of days non-stop? Did you start that PostgreSQL DB? Did you start MySQL? Did you start Apache? Tor? Privoxy? ... Is it really your job to remember? > I'm not sure the patch in the PR is right (mostly for lack of > examination or testing), but I'm wondering what people think about the > general idea of having the shutdown action ignore whether _enable is on? I'm running with variations of this for more than a year and not once have I been able to detect unwanted side effects. However, I can assure you it has spared me a lot of problems. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?