Use /etc/cron.d Over Crontab.

Not all background jobs have to be in the main crontab (the one you see at EDITOR=vi crontab -e ). That crontab was all I ever knew, so the revelation of the /etc/cron.d directory was helpful, to say the least. Some benefits include:

  1. Can separate different systems into different files
    (can’t edit /etc/cron.d/database_maintenance and accidentally screw up your stock algorithm, because that’s in…

Harvard. Software Engineer. American.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The importance of documentation for Remote Teams — Part I

Investment Series: PagerDuty, Disqus, and MemSQL

Scaling at Instacart: Distributing Data Across Multiple Postgres Databases with Rails

Difference between OOP and POP

API request to Azure DevOps from PowerShell

5 Musical Instruments Made Only with CSS

Keyboard, Drum Kit, Electric Guitar, Acoustic Guitar, and a Bass Guitar all made using CSS

Choosing a Data Storage Approach

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
James Fulford

James Fulford

Harvard. Software Engineer. American.

More from Medium

Read the documentation first

What is Varnish and how does it work?

Fixing “add-apt-repository command not found” error on Ubuntu and Debian

Setting up Data Collection