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. jamesfulford.com

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

Recommended from Medium

Amazon DynamoDB Deep Dive. Chapter 2: Tables, Data types, Indexes, Capacity Units

30 Things I Learned About Software Before I Turned 30

Managing secrets within an iOS app

Memo — Layered Decentralized Data Storage Middleware

Java — How to deal with ConcurrentModificationException in Java | Code Factory

Paste in SHA1 key: what? where? how?

Learning Experience with Codewayy.

AWS Lambda Security Checklist — Don’t become SecureLess

Lambda Security Checklist

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. jamesfulford.com

More from Medium

DCA Trading Bot in Julia and Python

Open Source Investment Research for Everyone

TheRockTrading Python Library

Metatrader +Python +Telegram