From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6297 invoked from network); 9 Dec 2020 02:01:39 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 9 Dec 2020 02:01:39 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 35B5C944D7; Wed, 9 Dec 2020 12:01:33 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id A72EC944D6; Wed, 9 Dec 2020 12:01:02 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id 9F74E944D4; Wed, 9 Dec 2020 12:00:59 +1000 (AEST) Received: from nsstlmta31p.bpe.bigpond.com (nsstlmta31p.bpe.bigpond.com [203.38.21.31]) by minnie.tuhs.org (Postfix) with ESMTPS id 9F74E944D3 for ; Wed, 9 Dec 2020 12:00:58 +1000 (AEST) Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep31p-svc.bpe.nexus.telstra.com.au with ESMTP id <20201209020056.QXXO10680.nsstlfep31p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com> for ; Wed, 9 Dec 2020 13:00:56 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedujedrudejjedggeduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuuffpveftpgfvgffnuffvtfetpdfqfgfvnecuuegrihhlohhuthemucegtddtnecunecujfgurhepfffhvffujgfkfhgfgggtsehmtddtredtreejnecuhfhrohhmpeffrghvvgcujfhorhhsfhgrlhhluceouggrvhgvsehhohhrshhfrghllhdrohhrgheqnecuggftrfgrthhtvghrnhepieegteeivdevfeffudekhfegleduveejkedtgfefudekhfekleelvdejheetfeefnecukfhppeduuddtrddugedurdduleefrddvfeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheprghnvghurhhinhdrhhhorhhsfhgrlhhlrdhorhhgpdhinhgvthepuddutddrudeguddrudelfedrvdeffedpmhgrihhlfhhrohhmpeeouggrvhgvsehhohhrshhfrghllhdrohhrghequceuqfffjgepkeeukffvoffkoffgpdhrtghpthhtohepoehtuhhhshesthhuhhhsrdhorhhgqe X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean X-RG-VS-CLASS: clean Received: from aneurin.horsfall.org (110.141.193.233) by smtp.telstra.com (5.8.420) id 5F73BFB018D8EF5F for tuhs@tuhs.org; Wed, 9 Dec 2020 13:00:56 +1100 Received: from aneurin.horsfall.org (localhost [127.0.0.1]) by aneurin.horsfall.org (8.15.2/8.15.2) with ESMTP id 0B920tjK025883 for ; Wed, 9 Dec 2020 13:00:55 +1100 (EST) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by aneurin.horsfall.org (8.15.2/8.15.2/Submit) with ESMTP id 0B920sOV025880 for ; Wed, 9 Dec 2020 13:00:55 +1100 (EST) (envelope-from dave@horsfall.org) X-Authentication-Warning: aneurin.horsfall.org: dave owned process doing -bs Date: Wed, 9 Dec 2020 13:00:53 +1100 (EST) From: Dave Horsfall To: The Eunuchs Hysterical Society In-Reply-To: Message-ID: References: <20201208190539.GA3303@mcvoy.com> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) X-GPG-Public-Key: http://www.horsfall.org/gpgkey.pub X-GPG-Fingerprint: 05B4 FFBC 0218 B438 66E0 587B EF46 7357 EF5E F58B X-Home-Page: http://www.horsfall.org/ X-Witty-Saying: "chmod 666 the_mode_of_the_beast" MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1483753691-947292162-1607479255=:25789" Subject: Re: [TUHS] Were cron and at done at the same time? Or one before the other? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1483753691-947292162-1607479255=:25789 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 8 Dec 2020, Michael Kjörling wrote: > If you have at but not cron, then implementing the other doesn't seem > quite as straightforward. It would certainly still be possible, but it > would definitely give rise to the question of "wouldn't it be real nice > if I could set this task up to run on a recurring basis?" followed by > "wouldn't it make more sense for the run-stuff-at-some-time task to run > from the recurring-execution tool, than the other way around?". I've never seen a *nix (since the 70s) that didn't have CRON (in one form or another)... And on my FreeBSD system, "atrun" is called every 5 minutes, so /etc/crontab will need to be edited for finer granularity. -- Dave --1483753691-947292162-1607479255=:25789--