Bash Shell Scripting for Linux and Unix Environments

🐧 Cron Jobs Explained (Automate Tasks in Linux) Doing the same task every day? Automate it. ⏰ What is a Cron Job? A cron job is a scheduled task in Linux that runs automatically at a specific time or interval. 📅 Cron Format "* * * * * command" Minute | Hour | Day | Month | Day of Week ⚙️ Common Examples 🕛 Run every day at midnight "0 0 * * * /path/script.sh" ⏳ Run every 5 minutes "*/5 * * * * command" 🛠️ Useful Commands "crontab -e" → Edit cron jobs "crontab -l" → List cron jobs 🚀 Use Cases • Backups • Log cleanup • System monitoring scripts • Scheduled updates ⚠️ Common Mistakes • Wrong time format • Missing execution permissions • Incorrect script paths 💡 Key Insight Automating repetitive tasks saves time and reduces human errors. #Linux #DevOps #Automation #Cron #SystemAdmin #CloudEngineer #LinuxCommands

Until now, I was running Linux commands one by one. Today I started learning how to automate them. That’s what I explored while getting into shell scripting in Linux. Instead of manually executing commands every time, I practiced how to write simple scripts that can run multiple steps automatically. What I practiced today: ✔ Creating a basic shell script (".sh" file) ✔ Understanding the shebang ("#!/bin/bash") ✔ Writing simple commands inside a script ✔ Running scripts using "bash" ✔ Making scripts executable with "chmod +x" What stood out: This felt like a big shift. Instead of repeating the same commands again and again, scripting allows you to automate workflows which is exactly what real DevOps and system administration work depends on. Hands-on progress: ✔ Created my first shell script ✔ Executed multiple commands through a script ✔ Understood how Linux runs scripts ✔ Learned how execution permissions affect scripts Key takeaway 💡 Running commands is useful. Automating them is powerful. This is where Linux starts becoming a real engineering tool. #Linux #DevOps #ShellScripting #Automation #SystemAdministration #Infrastructure #TechLearning

DevOps Zero to Job-Ready – Day 12/180 | Conditionals & Loops in Bash Scripts shouldn’t run blindly — they should react based on conditions. Conditionals (`if`) allow decisions like checking if a file or server exists. Loops (`for`, `while`) help repeat tasks across files, logs, or retries. This is what makes scripts dynamic instead of static commands. More structured DevOps notes and scenarios available on [www.engidock.com] #DevOps #Linux #Automation

DevOps Zero to Job-Ready – Day 14/180 | Backup Automation Script This is where scripting becomes real. Instead of isolated commands, a script now solves an actual problem — automating backups. Creating archives, naming them with dates, and running without manual effort. No one should remember to take backups — it should just happen. More structured DevOps notes and scenarios available on www.engidock.com. Next: Networking basics (IP & DNS) #DevOps #Linux #Automation

Day 07 of #90DaysOfDevOps 🚀 Linux File System Hierarchy: Know Where Everything Lives Today I stopped treating Linux as a black box. Time to think like an operator. Every DevOps engineer should know where to look first: → `/etc` — configuration files (nginx, ssh, hosts) → `/var/log` — first stop during incidents → `/tmp` — temporary files → `/opt` — third-party tools (Jenkins, Grafana) → `/home` / `/root` — user environments and permissions What I practiced today: ✅ Mapped core Linux directories with real-world use cases ✅ Diagnosed a failed service using `systemctl status` + `journalctl` ✅ Identified CPU-heavy processes with `ps aux --sort=-%cpu` ✅ Resolved permission issues using `chmod +x` ✅ Located service logs with `journalctl -u <service>` 💡 Most useful takeaway: A service failing after reboot isn't always a crash issue — sometimes it was never enabled to start. Verified with `systemctl is-enabled`. 🔑 Mindset Shift: In production, speed comes from knowing where to check, what to run, and what signal matters first. #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Linux #DevOps

Day 7/100 – Setting Up Password-less SSH Authentication in Linux It's Day 7 already. 🎉 Today, I was presented with another real world DevOps challenge; To implement password-less SSH access between a jump host and multiple app servers. The goal was to allow a user (thor) on the jump host to connect to other servers using their respective sudo users without being prompted for a password. This is especially important for scripts that run automatically and need uninterrupted access (like the cron job worked on yesterday). The first thing I did was to generate an SSH key pair using "ssh-keygen -t rsa" and distribute the public key to each app server using "ssh-copy-id". Once that was done, I tested the connections and confirmed that access was successful without any password prompts. Password-less access is essential for cron jobs and scripts. Security is about balance: automation vs controlled access and knowing when each is desired. This is one of those behind-the-scenes setups that makes CI/CD pipelines, remote scripts, and large-scale infrastructure actually work. One day at a time till perfection.🚀 #DevOps #CloudEngineering #Linux #SSH #TechLearning #100DaysOfCode # #SystemAdministration #LearningInPublic

In this lab, I build a user management script that prompts for a username, creates the account, sets a password, and adds the user to a group. It shows how Bash can take user input and turn it into automated system commands. This lab also helps me practice system administration while improving my Bash scripting skills. #Linux #Bash #ShellScripting #SystemAdministration #DevOps #Automation

Most people think “maintenance mode” means shutting everything down. But in real-world systems, that’s not how it works. I built a small project to explore how Linux servers actually handle maintenance using systemd (.targets) + Nginx + automation scripts. Instead of killing the server, this setup: Keeps SSH access alive Keeps Nginx running Switches traffic to a maintenance page Uses a custom maintenance.target to control the system state Automates everything through a single script The idea was to understand how targets and services work together in systemd, and how this concept is applied in real DevOps environments. It’s a simple setup (just two HTML pages), but it demonstrates a powerful concept: controlled downtime instead of a total shutdown Project link: https://lnkd.in/e7-SV5T3 Would love to hear feedback or suggestions. #linux #DevOps #systemd

🚀 Strengthening my expertise in Shell Scripting Focused on building efficient scripts to automate routine tasks and improve system reliability. Working with control structures, variables, and real-world automation use cases is helping me develop a deeper understanding of scalable and maintainable solutions. Consistency and continuous learning are key to delivering better, faster, and more reliable systems. 💻⚙️ #ShellScripting #Linux #DevOps #Automation #Bash #CloudComputing #Scripting #TechSkills #SystemAdministration #DevOpsEngineer

⚡ The Power of Bash / Shell In the world of technology, speed, control, and automation matter more than ever. 👉 That’s where Bash/Shell becomes a game changer. 💡 Why Bash is so powerful? 🔹 Direct control over your system 🔹 Automate repetitive tasks in seconds 🔹 Chain commands to build powerful workflows 🔹 Lightweight, fast & efficient 🔹 Works across Linux, macOS & even Windows (WSL) 🚀 Real Power of Bash With Bash, you can: ✅ Automate backups ✅ Deploy applications ✅ Monitor logs ✅ Clean systems ✅ Manage servers like a pro 👉 Do in seconds what takes minutes in GUI!. 🧠 Why it matters? ✔ Saves time ✔ Reduces human errors ✔ Boosts productivity ✔ Essential skill for Developers & DevOps Engineers 💬 Final Thought. Bash is not just a tool… it’s a SUPERPOWER. 💪 Learn it. Master it. Automate your world. 📌 Follow me on LinkedIn to get more such content 🌐 www.goldenwebportal.com #Bash #ShellScripting #Linux #DevOps #Automation #Programming #TechSkills #Developers #CloudComputing #ITSkills #LearnToCode #Productivity #SystemAdmin #GoldenSpotDigitalWorld