Error Handling in Bash for Reliable Scripts

Writing Files in Bash✍️ Reading files is useful🧐 But writing them is where things get interesting. In Bash, you don’t “open and save” files. You redirect output into them. echo "hello world" > output.txt That single > means: overwrite the file If you want to keep existing data: echo "new line" >> output.txt That’s the append operator. This is one of those small concepts that quietly powers everything:  • logs  • automation scripts  • system reports Once you get used to this, text files become your database. #Bash #Linux #Terminal #DevOps #Programming CoderCo

Day 22 of my 30 Days of Learning Linux with the Data Engineering Community Today, I explored conditional statements in Bash scriptingspecifically "if" and "if-else". These are powerful tools that help control the flow of a script by executing commands only when certain conditions are met. Understanding how to make decisions within scripts is a key step toward writing more dynamic and efficient automation in data workflows. #Linux #DataEngineering #BashScripting #LearningJourney

Day 25 of the 30 Days of Linux Challenge with Data Engineering Community was all about making Bash scripts think before they act. Today I learned how conditional statements and loops work in Bash. I explored if, if-else, and if-elif-else, along with common comparison operators for files, strings, and numbers. I also looked at how conditions can be combined with AND and OR, how the case statement helps with multiple matches, and how for and while loops can be used to repeat tasks more efficiently. What I liked most about today’s lesson was seeing how these concepts make Bash scripts more practical and dynamic. It is one thing to run commands, but it is another thing to make scripts respond to different situations and automate repeated work more intelligently. Grateful to the DEC community for this challenge and for the steady learning structure. Day by day, things are starting to connect. #30DaysOfLinux #Linux #BashScripting #DataEngineering #LearningInPublic

Working with files in Bash comes down to 3 essential skills: 📖 Reading Files Use a while loop to process a file line-by-line (best for scripts), or cat for quick viewing or piping into other commands. ✍️ Writing Files - > → creates or overwrites a file - >> → appends to an existing file without deleting content 🔐 Checksums (File Integrity) Commands like md5sum or sha256sum generate a unique “fingerprint” of a file. If two files have the same checksum → they’re identical. If not → something changed. 👉 Why this matters: These basics power automation, data processing, and security checks in real-world scripts. #Bash #Linux #DevOps #Programming #Automatio

Day 1 of learning Bash. Built a system info reporter from scratch. It pulls: → Hostname, OS, kernel version → Uptime → Disk usage \(df -h\) → RAM usage \(free -m\) → Top 5 CPU processes \(ps aux --sort=-%cpu\) One script. One command. Readable output. Four things that actually stuck: ① $? isn't optional every command returns an exit code. Ignore it and you're scripting blind. ② String manipulation is built-in $\{var/old/new\}, $\{#array\[@\]\}, $\{var##\*/\}. No need to pipe everything through sed for simple ops. ③ 2\>/dev/null isn't lazy it's intentional. Suppress errors users don't need to see; log them where you do. ④ printf over echo echo is for quick checks. printf gives you format control: columns, padding, consistent output. Code is on GitHub. Rough, but working. Committing daily for 4 days. If you're learning Bash or Linux, drop a comment — happy to share notes. #Bash #Linux #DevOps #ShellScripting #LearningInPublic

Day 33/41 — I learned how to work with files inside Bash scripts. After learning how to take user input, today I explored how scripts can interact with files. 👉 1. Check if a file exists Example: if [ -f "file.txt" ] then echo "File exists" else echo "File not found" fi 👉 2. Create a file Example: touch newfile.txt 👉 3. Write to a file Example: echo "Hello Linux" > file.txt 👉 Overwrites content 👉 4. Append to a file Example: echo "New line" >> file.txt 👉 Adds content without deleting existing data 👉 5. Read a file Example: cat file.txt 💡 What I noticed: Scripts can not only run commands, they can also manage files automatically. 💡 Example use case: • Check if a file exists before using it • Write logs to a file • Automate file creation and updates This feels very useful for real-world scripting. Tomorrow I’ll explore working with loops + files together. If you use Linux — do you automate file handling in scripts?

Day 26 of the 30 Days of Linux Challenge with Data Engineering Community was focused on functions and reusability in Bash. Today I learned how functions help reduce repetition and make Bash scripts cleaner and easier to maintain. I explored how to define and call functions, how to pass parameters using $1, $2, and $@, how return values and exit codes work, and why local variables matter inside functions. I also learned how functions can be combined to build more modular workflows and how utility functions can be reused across scripts with source. What stood out to me today was seeing how Bash can be structured in a much more organized way than I first thought. The more I learn, the more I see how these small concepts come together to build practical automation. Grateful to the DEC community for putting this challenge together and for making the learning journey steady and hands-on. #30DaysOfLinux #Linux #BashScripting #DataEngineering #LearningInPublic

Day 32/41 — I learned how to take user input in Bash scripts. Until now, my scripts were fixed — they always ran the same way. Today I explored how to make them interactive using input. 👉 1. read Used to take input from the user Example: read name 👉 Waits for user input and stores it in name 👉 Using the input: echo "Hello, $name" 👉 2. Prompt with message: read -p "Enter your name: " name 👉 Displays a message before taking input 👉 3. Silent input (for passwords): read -s password 👉 Hides input while typing 👉 Example script: #!/bin/bash read -p "Enter your name: " name echo "Welcome, $name" 💡 What I noticed: Scripts don’t have to be static — they can adapt based on user input. 💡 Example use case: • Take user data • Build interactive scripts • Accept dynamic input instead of hardcoding This makes scripting feel much more practical. Tomorrow I’ll explore working with files inside scripts. If you use Linux — have you tried interactive scripts?

Just built a User Management System using Bash Scripting 🐧💻 In this project, I created a menu-driven script to manage Linux users efficiently from the terminal. 🔹 Features: Add new users with validation Check existing users Delete users with confirmation Grant sudo privileges Fetch user details using id Display user list Clean terminal option This project helped me understand: Shell scripting concepts Conditional statements & loops Regex validation System-level commands like useradd, userdel, usermod Working with /etc/passwd 💡 Key Learning: Building real-world scripts improves problem-solving and gives better control over Linux systems. Still exploring and improving my scripting skills… 🚀 #Linux #AWS #DevOps #SystemAdministration #Rukna_nahi_hai🔥 #Never_stop♾️ #आता_थांबायच_नाय... Ethans Leads Ethans Tech LLP Jatin Miglani Nikhat Sayyed

Day 07/30 of Learning Linux with the Data Engineering Community Today’s session moved beyond basic file handling into something much closer to real data workflows: file validation and direct data downloads from the terminal. I learned and practiced two highly practical Linux commands: - wc File measurement and validation Used wc to count: - lines - words - bytes - characters - longest line This was especially useful for checking whether my sample datasets (countries.txt and capitals.txt) still had the correct number of rows after edits. One simple but powerful lesson: line count is one of the fastest data quality checks you can do before analysis. A quick wc -l can instantly tell you if records are missing. - wget Downloading files directly from the web This command made Linux feel even more practical. I learned about: - downloading files from URLs - running downloads in the background - resuming interrupted downloads - recursive downloads - downloading multiple URLs from a file This is the exact kind of workflow used when pulling datasets, scripts, logs, or documentation directly into Linux environments. The biggest takeaway from today: Linux is not just for navigating folders. It can validate datasets and collect external data without needing a browser. That makes it incredibly useful for data engineering workflows. 🔗 GitHub / Documentation Link: https://lnkd.in/eTm2SkPc #Linux #DataEngineering #GitHub