From owner-freebsd-arch@freebsd.org Sun Feb 9 13:38:00 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 A002123988D for ; Sun, 9 Feb 2020 13:38:00 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48FqqC2SLdz49Fv for ; Sun, 9 Feb 2020 13:37:58 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id 0mmXjpM1NkqGX0mmZjtz8k; Sun, 09 Feb 2020 06:37:57 -0700 X-Authority-Analysis: v=2.3 cv=c/jVvi1l c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=l697ptgUJYAA:10 a=IPjA-QJCAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=Chdz1smtSHJfnHFK3T0A:9 a=QEXdDO2ut3YA:10 a=rd03tn_Jzo6Lv0OJAoBv:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [192.168.1.105] (S0106002401cb186f.gv.shawcable.net [70.67.125.17]) by spqr.komquats.com (Postfix) with ESMTPSA id 230201558; Sun, 9 Feb 2020 05:37:53 -0800 (PST) Date: Sun, 09 Feb 2020 05:37:51 -0800 User-Agent: K-9 Mail for Android In-Reply-To: <8967.1581243035@critter.freebsd.dk> References: <6701.1581190231@critter.freebsd.dk> <97A66670F59C9C626B5090E3@triton.njm.me.uk> <8967.1581243035@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: updating cron and atrun To: freebsd-arch@freebsd.org, Poul-Henning Kamp , "N.J. Mann" From: Cy Schubert Message-ID: <55C50689-6DA8-4D44-92BB-72C38B54AC96@cschubert.com> X-CMAE-Envelope: MS4wfI3RDfzk3kSE5bna6iGjsNGKQ/vCy6OuZjjtXjLE5PP9vMJozRyWzW2DNAz4i2GsA7ZWinnYfStHBwg2+IHumQbQmMJGIeuZ2hIcNm5ySuvpv8DCRF28 GjgQcmfAIJPXbRz6PgUCTtEqBt4fjRDAXmLhxj99Dr2kdc/BvK3v/GbBXJuKxfxaAQ95d4hzSKOW54QDFAC32X5Oqf/Vq57QCWoDdd3pMMuJEdIhcGSC1Q+V 1efgapK7QxkC8vZd2F6L3A== X-Rspamd-Queue-Id: 48FqqC2SLdz49Fv X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.134.9) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-4.68 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RWL_MAILSPIKE_GOOD(0.00)[9.134.59.64.rep.mailspike.net : 127.0.0.18]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[9.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.48)[ip: (-6.60), ipnet: 64.59.128.0/20(-3.21), asn: 6327(-2.50), country: CA(-0.09)]; 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 13:38:00 -0000 On February 9, 2020 2:10:35 AM PST, Poul-Henning Kamp wrote: >-------- >In message <97A66670F59C9C626B5090E3@triton=2Enjm=2Eme=2Euk>, "N=2EJ=2E M= ann" >writes: >>Hi, >> >>On Saturday, February 08, 2020 19:30:31 +0000 Poul-Henning Kamp wrote: >>>=20 >>> Thanks for looking into this=2E >>>=20 >>> Is at(1) something people actually use these days, or should it be >>> disabled by default ? >> >>I do=2E I use it to run various homebrew scripts in response to >external >>events=2E I needed a delay (sometime minutes, sometimes hours) between >>the event and the response and at(1) was a perfect fit=2E > >Right, it is absolutely useful to have, if you need it, and it should >not be removed=2E > >But if, as I suspect, the vast majority of FreeBSD pointlessly add=20 >288 lines to /var/log/cron every day, without anybody ever using the >at(1) >command, maybe we should disable it to save power and disk-wear ? I use at at(1) and batch(1) all the time, on FreeBSD and other platforms= =2E Most people I know, professionally, don't know about these commands=2E = They add the 288 lines to cron every day=2E They're not interested when I e= xplain to them a better way to do it=2E What's worse, at $JOB, at(1) and ba= tch(1) have been uninstalled on Linux (while they remain on the other platf= orms) because the senior Linux person (who left our employ three weeks ago)= felt people didn't understand the utilities and, they could add anything t= o cron for a day if they wanted=2E=20 The idea of removing at(1) and batch(1) is not new=2E People generally hav= e no idea what they do and people are unwilling to chance using them or lea= rning something new because they're busy working=2E That's my experience=2E= =20 --=20 Pardon the typos and autocorrect, small keyboard in use=2E=20 Cy Schubert FreeBSD UNIX: Web: https://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E