From owner-freebsd-arch@freebsd.org Sun Feb 9 09:22:05 2020 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2BEB023287D for ; Sun, 9 Feb 2020 09:22:05 +0000 (UTC) (envelope-from njm@njm.me.uk) Received: from smtp002.apm-internet.net (smtp002.apm-internet.net [85.119.248.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48Fk7v73jWz3P1M for ; Sun, 9 Feb 2020 09:22:03 +0000 (UTC) (envelope-from njm@njm.me.uk) Received: (qmail 91386 invoked from network); 9 Feb 2020 09:22:01 -0000 X-APM-Authkey: 18389/1(18389/1) 2 Received: from unknown (HELO meld.njm.me.uk) (86.157.235.207) by smtp002.apm-internet.net with SMTP; 9 Feb 2020 09:22:01 -0000 Received: from triton.njm.me.uk (triton.njm.me.uk [192.168.144.133]) by meld.njm.me.uk (8.15.2/8.15.2) with ESMTP id 0199M18J022686; Sun, 9 Feb 2020 09:22:01 GMT (envelope-from njm@njm.me.uk) Received: from localhost (localhost [127.0.0.1]) by triton.njm.me.uk (8.15.2/8.15.2) with ESMTP id 0199M0s3052876; Sun, 9 Feb 2020 09:22:00 GMT (envelope-from njm@njm.me.uk) Date: Sun, 09 Feb 2020 09:22:00 +0000 From: "N.J. Mann" To: Poul-Henning Kamp cc: freebsd-arch@freebsd.org Subject: Re: updating cron and atrun Message-ID: <97A66670F59C9C626B5090E3@triton.njm.me.uk> In-Reply-To: <6701.1581190231@critter.freebsd.dk> References: <6701.1581190231@critter.freebsd.dk> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Rspamd-Queue-Id: 48Fk7v73jWz3P1M X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of njm@njm.me.uk has no SPF policy when checking 85.119.248.221) smtp.mailfrom=njm@njm.me.uk X-Spamd-Result: default: False [0.11 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.863,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.13)[-0.131,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[njm.me.uk]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[221.248.119.85.list.dnswl.org : 127.0.3.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35259, ipnet:85.119.248.0/21, country:GB]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(0.31)[ipnet: 85.119.248.0/21(0.90), asn: 35259(0.72), country: GB(-0.08)]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2020 09:22:05 -0000 Hi, On Saturday, February 08, 2020 19:30:31 +0000 Poul-Henning Kamp wrote: > > Thanks for looking into this. > > Is at(1) something people actually use these days, or should it be > disabled by default ? I do. I use it to run various homebrew scripts in response to external events. I needed a delay (sometime minutes, sometimes hours) between the event and the response and at(1) was a perfect fit. Cheers, Nick. --