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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24844 invoked from network); 8 Dec 2020 19:40:53 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 8 Dec 2020 19:40:53 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 22C7E944FC; Wed, 9 Dec 2020 05:40:49 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id CFC38944D4; Wed, 9 Dec 2020 05:40:31 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="TwKpCikA"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id C51F2944D4; Wed, 9 Dec 2020 05:40:26 +1000 (AEST) Received: from mail-qv1-f45.google.com (mail-qv1-f45.google.com [209.85.219.45]) by minnie.tuhs.org (Postfix) with ESMTPS id 02D1E944D3 for ; Wed, 9 Dec 2020 05:40:25 +1000 (AEST) Received: by mail-qv1-f45.google.com with SMTP id bd6so3597517qvb.9 for ; Tue, 08 Dec 2020 11:40:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S+UNCpuRGSKdS8aFppVEtKMfDQnJWItaT59Llb8Z7Jc=; b=TwKpCikALux8494+tdAph1YpGQAtzhr6jkeW6TDXprY8584ELoxIXtJ5aaS2hOhSxW wTiWbRV5MCTgXBCKNMIjTZ128EZSTfHieempJ8z5ChZJR44a2qKPp4kbbEKhlNoBo6PX 0LrEH1eGP72TqP3x8qPRDEe2imzH1AH6/nCCs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=S+UNCpuRGSKdS8aFppVEtKMfDQnJWItaT59Llb8Z7Jc=; b=S88i4MyC7fbFA+hkkDK6kTJuijX+1QuJMtEz7qNNVvWqUN/ednsbUKc4Ddj9mYoznR K+MjFQBSx2+whjRcZUe8sCY3urCoEDEsaYwDKta0K6Vj8eklnzUhbySy01zJGcnEtki6 kWJPja2JtLQPr8fn8oLTbSXVeAGFMvyGRptrz5eynIE3ZpDlwbdxuX+asFcOATtFtsyz o2/J8Z1gKe5LCueoWThrhJ+8mw9vq2KcWPa1ZRfqTJLGe1/eG/elhTO2BxmtEMfaflp6 MUdc1Cx6moQckSrWibxLPwi1763bWh1CjszMWkJcaNfJP04WbTF2x3xyyiZXMlazzK6A Un1Q== X-Gm-Message-State: AOAM5327MwNp7mu8D/URM/FncqGBc43jX1xIrOg5jq3JOjNrr/IkRQ5p LH+2UFHlzgXrp9GHVlXPrpb31zd3+5STVK/rv1sKbg== X-Google-Smtp-Source: ABdhPJx/Mgue+K1yAwQDzkxdXe5bOP+59ffHlpXyMApjCSXCcYnnDyRZFJ+JDOteSv3x6wurOYbpcFdnBK8ewS5LQHQ= X-Received: by 2002:a05:6214:10e3:: with SMTP id q3mr29732155qvt.3.1607456424776; Tue, 08 Dec 2020 11:40:24 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Clem Cole Date: Tue, 8 Dec 2020 14:39:58 -0500 Message-ID: To: Mary Ann Horton Content-Type: multipart/alternative; boundary="00000000000030eb4705b5f91dfa" 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: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000030eb4705b5f91dfa Content-Type: text/plain; charset="UTF-8" Correct. at was a v7-ism. Trying to put a nicer face on the idea - that is to say, I looked at the "at" command as a user-mode (command) front-end to cron so you didn't have to edit the crontab yourself. The later had been around as a system support idea, since at least 6th edition - maybe 5th. On Tue, Dec 8, 2020 at 1:51 PM Mary Ann Horton wrote: > My V6 manual has cron(VIII) - documentation of /usr/lib/crontab - but no > mention of at. > > This is consistent with my recollection - I first saw at in V7. > > Mary Ann > > On 12/8/20 10:11 AM, ron minnich wrote: > > When I got into Unix in 1976 cron and at were both there. > > > > I got to wondering for no particular reason which came first -- I had > > always assumed cron, but ...? > > > > Anyone know? > --00000000000030eb4705b5f91dfa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Correct.=C2=A0 at was a v7-ism.=C2=A0 =C2=A0Trying to p= ut a nicer face on the idea - that is to say, I looked at the "at"= ; command as a user-mode (command) front-end to cron so=C2=A0you didn't= have to edit the crontab yourself.=C2=A0 The later had been around as a sy= stem support idea, since at least 6th edition - maybe 5th.

<= div class=3D"gmail_quote">
On Tue, Dec= 8, 2020 at 1:51 PM Mary Ann Horton <= mah@mhorton.net> wrote:
My V6 manual has cron(VIII) - documentation of /usr/lib/cron= tab - but no
mention of at.

This is consistent with my recollection - I first saw at in V7.

=C2=A0=C2=A0=C2=A0=C2=A0 Mary Ann

On 12/8/20 10:11 AM, ron minnich wrote:
> When I got into Unix in 1976 cron and at were both there.
>
> I got to wondering for no particular reason which came first -- I had<= br> > always assumed cron, but ...?
>
> Anyone know?
--00000000000030eb4705b5f91dfa--