From owner-freebsd-questions@freebsd.org Wed Feb 22 13:18:35 2017 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 1F57BCE99F7 for ; Wed, 22 Feb 2017 13:18:35 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9020698A for ; Wed, 22 Feb 2017 13:18:34 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v1MD8BgX085329; Thu, 23 Feb 2017 00:08:11 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 23 Feb 2017 00:08:11 +1100 (EST) From: Ian Smith To: Adam Vande More cc: Chris Stankevitz , freebsd-questions@freebsd.org Subject: Re: passing -t to newsyslog In-Reply-To: Message-ID: <20170222233954.J37376@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 13:18:35 -0000 In freebsd-questions Digest, Vol 664, Issue 3, Message: 9 On Tue, 21 Feb 2017 21:19:40 -0600 Adam Vande More wrote: > On Tue, Feb 21, 2017 at 8:36 PM, Chris Stankevitz wrote: > > I want "-t" to be passed when newsyslog is run hourly... not when it is > > run once when the system boots for the purpose of creating log files. > > > > Per "man rc.conf": > > > > newsyslog_enable is used to run newsyslog one time at boot to create > > missing log files. newsyslog_enable does not cause newsyslog to > > continuously run. > > > > Per /etc/crontab: > > > > newsyslog is run periodically via en entry in /etc/crontab. newsyslog is > > called without any arguments. > There is no law preventing you from editing /etc/crontab. I imagine that > bit of advice is there so the system's crontab isn't broken. > > Setting correct locale may also fulfill your desires assuming LC_TIME is > read. While Matthew well advises using user crontabs where appropriate, this is one case where it's likely best to edit /etc/crontab directly. I've never had qualms about editing /etc/crontab, and do so often, but to address concerns about source or binary upgrades, sufficient backup becomes something like # cp -p /etc/crontab /root/crontab.mine cheers, Ian