From owner-freebsd-chat@FreeBSD.ORG Wed Mar 16 16:22:00 2011 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8158A1065670 for ; Wed, 16 Mar 2011 16:22:00 +0000 (UTC) (envelope-from jamie@geniegate.com) Received: from geniegate.com (geniegate.com [65.18.174.84]) by mx1.freebsd.org (Postfix) with ESMTP id 3C8778FC14 for ; Wed, 16 Mar 2011 16:21:59 +0000 (UTC) Received: from geniegate.com (geniegate.com [65.18.174.84]) by geniegate.com (8.14.2/8.14.2) with ESMTP id p2GGRFWA013440 for ; Wed, 16 Mar 2011 16:27:15 GMT (envelope-from jamie@geniegate.com) Received: from localhost (localhost [[UNIX: localhost]]) by geniegate.com (8.14.2/8.14.2/Submit) id p2GGRFvd013439 for freebsd-chat@freebsd.org; Wed, 16 Mar 2011 16:27:15 GMT (envelope-from jamie@geniegate.com) X-Authentication-Warning: geniegate.com: joe set sender to jamie@geniegate.com using -f Date: Wed, 16 Mar 2011 11:21:55 -0500 From: Jamie To: freebsd-chat@freebsd.org Message-ID: <20110316162155.GF2565@apollo.podro.com> References: <20110316133154.GE2565@apollo.podro.com> <86y64fw1j6.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86y64fw1j6.fsf@ds4.des.no> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Odd cron errors X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2011 16:22:00 -0000 On Wed, Mar 16, 2011 at 04:03:25PM +0100, Dag-Erling Sm??rgrav wrote: > Jamie writes: > > I actually very much do NOT want atrun to be tinkering with the > > priority (as I'd like to have it run in the idle task eventually) > > > > Is there a way, short of recompiling, that I can convince atrun > > not to do this? > > How about disabling atrun? I use at/batch *constantly* (especially batch) The machine I'm replacing was setup to run cron under idprio 31 (outside the jail) specifically so that jobs ran during the idle task. Disabling is a no-go. Jamie -- http://www.geniegate.com Custom web programming Perl * Java * UNIX User Management Solutions