From owner-freebsd-questions@FreeBSD.ORG Thu Dec 5 00:09:13 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11A79E32 for ; Thu, 5 Dec 2013 00:09:13 +0000 (UTC) Received: from know-smtprelay-omc-10.server.virginmedia.net (know-smtprelay-omc-10.server.virginmedia.net [80.0.253.74]) by mx1.freebsd.org (Postfix) with ESMTP id 7ABB81CE9 for ; Thu, 5 Dec 2013 00:09:09 +0000 (UTC) Received: from amd.asgard.uk ([92.238.71.115]) by know-smtprelay-10-imp with bizsmtp id xc8x1m00K2VE8Jc01c8zu8; Thu, 05 Dec 2013 00:09:01 +0000 X-Originating-IP: [92.238.71.115] X-Spam: 0 X-Authority: v=2.1 cv=Qfbov6rv c=1 sm=1 tr=0 a=kgu37eZCuzjHC/BLjkfnNA==:117 a=kgu37eZCuzjHC/BLjkfnNA==:17 a=mSnCZvPJBnkA:10 a=g8DGSEr-gRIA:10 a=z6OmtuC8ihAA:10 a=8nJEP1OIZ-IA:10 a=U4kjxnpeAAAA:8 a=RIXHdJ6alCwA:10 a=XZIQ03Hw2ihuBsw9AdEA:9 a=wPNLvfGTeEIA:10 From: dgmm To: freebsd-questions@freebsd.org Subject: Re: System reboots ~3am during daily periodic 450.status-security run Date: Thu, 5 Dec 2013 00:08:54 +0000 User-Agent: KMail/1.13.7 (FreeBSD/9.1-RELEASE-p7; KDE/4.10.5; amd64; ; ) References: <201312012352.01075.freebsd01@dgmm.net> <201312031144.40570.freebsd01@dgmm.net> <529E6F80.7050705@ShaneWare.Biz> In-Reply-To: <529E6F80.7050705@ShaneWare.Biz> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201312050008.54995.freebsd01@dgmm.net> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 00:09:13 -0000 On Tuesday 03 December 2013 23:55:44 Shane Ambler wrote: > On 03/12/2013 22:14, dgmm wrote: > > On Tuesday 03 December 2013 09:48:04 krad wrote: > >> or you could use the @reboot option, that would mean it always runs at > >> crons start, which may not be what you want, > > > > Yes, that was my first thought but the overheads at boot time might be > > inconvenient although I'll try it to find out. > > Or write a rc script to run it at shutdown? Thanks. That's the answer I was looking for. There's no downside. It doesn't matter if it take longer to shut down and in general it gets shut fown every day.