I agree. I use /etc/cron.hourly /etc/cron.daily to set up automate processes for my slackware system. I found this article useful in distrowatch.com. This article explain what is crontab, for educational purposes.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
Heh... I'm too much of a control-freak to like using files in /etc/cron.<time-span>/. Using /etc/cron.hourly is fine, but as you move on to /etc/cron.<daily|weekly|monthly> the scheduling-control just feels to indefinite. I mean, I'm not even super fond of the Jenkins-scheduler's H option.
That said, for some tasks that I dump into /etc/cron.d/<service>, those scripts have backoff-randomizers to help avoid concurrency-related load-spikes that having a bunch of systems on the same schedule can cause. Doesn't feel great, but, sometimes you have to make concessions to resource-limitations.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree. I use /etc/cron.hourly /etc/cron.daily to set up automate processes for my slackware system. I found this article useful in distrowatch.com. This article explain what is crontab, for educational purposes.
Heh... I'm too much of a control-freak to like using files in
/etc/cron.<time-span>/. Using/etc/cron.hourlyis fine, but as you move on to/etc/cron.<daily|weekly|monthly>the scheduling-control just feels to indefinite. I mean, I'm not even super fond of the Jenkins-scheduler'sHoption.That said, for some tasks that I dump into
/etc/cron.d/<service>, those scripts have backoff-randomizers to help avoid concurrency-related load-spikes that having a bunch of systems on the same schedule can cause. Doesn't feel great, but, sometimes you have to make concessions to resource-limitations.