Goal today: replace a worn 11-speed cassette on my commuter and measure chain stretch while the...
Private by default — share only the days you choose.
No comments yet. Be the first to comment!
Sign in to leave a comment.
Goal today: replace a worn 11-speed cassette on my commuter and measure chain stretch while the...
Goal for today: true the rear wheel on my commuter after noticing a 2 mm lateral wobble at the rim...
Goal for today: bleed the rear hydraulic brake on my commuter before a longer ride Saturday. The...
Goal was to bleed the rear hydraulic on my neighbor's commuter — a Shimano MT200 lever and caliper...
Goal for today: true the rear wheel on my commuter after it started rubbing the brake pad on the...
Spent this morning finally automating my daily backup routine after losing three hours of work last week to a random laptop freeze. The sound of my old external drive clicking away in the background used to stress me out—now it's just white noise that means my system is doing its job.
Here's what I set up, step by step. First, I grabbed a simple backup script template and dropped it in my home directory. Then I opened crontab with crontab -e and added a line to run it every day at 2 AM when I'm definitely asleep. The syntax looked scary at first—all those asterisks and numbers—but it's just: minute, hour, day, month, weekday, then your command.
The checklist:
rsync --version to check)crontab -eMy mistake? I forgot to make the script executable with chmod +x. Spent fifteen minutes wondering why cron wouldn't run it. The error log just said "Permission denied" and I felt like an idiot. One quick chmod +x backup.sh fixed everything.
One thing I tried differently: instead of backing up everything, I made a small test folder with just five files. Ran the backup, checked the destination, confirmed the timestamp. Much better than backing up 50GB and hoping for the best.
Common mistake to avoid: Don't use relative paths in cron scripts. Cron doesn't run from your home directory, so ./Documents won't work. Use full paths like /home/sam/Documents or you'll be hunting bugs for hours.
Your tiny task: Open your terminal right now and type crontab -l. If it's empty or returns an error, you have no scheduled tasks. That's fine—but at least you know. If you see tasks you don't recognize, maybe it's time to audit what's running on your machine.
I tested the whole thing three times today with different file sizes. The third test used a 2GB video file just to see how long it would take. Forty seconds. Perfectly acceptable.
#automation #backup #productivity #terminal #techsetup