From owner-freebsd-questions@FreeBSD.ORG Sat Sep 3 18:07:04 2011 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B760106566C for ; Sat, 3 Sep 2011 18:07:04 +0000 (UTC) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [66.119.58.2]) by mx1.freebsd.org (Postfix) with ESMTP id C89DF8FC0A for ; Sat, 3 Sep 2011 18:07:03 +0000 (UTC) Received: from WildRover.lariat.net (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id MAA26269; Sat, 3 Sep 2011 12:06:57 -0600 (MDT) Message-Id: <201109031806.MAA26269@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 03 Sep 2011 12:06:56 -0600 To: Adam Vande More From: Brett Glass In-Reply-To: References: <201109031639.KAA25689@lariat.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: questions@freebsd.org Subject: Re: "at" command and mail X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 18:07:04 -0000 At 10:55 AM 9/3/2011, Adam Vande More wrote: >If you redirect the output from the command to /dev/null or other >file, you shouldn't recieve an email unless you've also specified -m. True. But that's awkward, and if you have a job that runs more than once, it'd be convenient to be able to keep the output from each run. I'd like to see a configuration option to send the output from each "at" job to a file in a directory -- one per job, automatically named -- rather than sending it out as e-mail. Or just not to keep it at all. (This could still be overridden with -m, of course.) In short, I'm looking for the sort of flexibility that's already built into periodic.conf, which allows you to specify whether output is mailed, sent to a file, or sent to /dev/null by default. This would be useful for lots of applications, and especially for embedded work. --Brett