updating cron and atrun

Poul-Henning Kamp phk at phk.freebsd.dk
Sun Feb 9 10:10:42 UTC 2020


--------
In message <97A66670F59C9C626B5090E3 at triton.njm.me.uk>, "N.J. Mann" writes:
>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.

Right, it is absolutely useful to have, if you need it, and it should
not be removed.

But if, as I suspect, the vast majority of FreeBSD pointlessly add 
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 ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


More information about the freebsd-arch mailing list