Automatic Linux Backup Script Guide for SysAdmins

https://www.linuxteck.com/automatic-linux-backup-script/

Practical Linux backup scripting using Bash, tar, rsync, cron jobs, SSH, logging, rotation, and email alerts.

#Linux #Bash #ShellScripting #DevOps #SysAdmin #LinuxAdmin #Automation

The Bash read command is what makes scripts interactive 🔧

Learn how to take user input, prompt users, and build smarter shell scripts 👇
https://www.linuxteck.com/bash-read-command-user-input-examples/

#Linux #Bash #DevOps #ShellScripting #OpenSource #LinuxTeck

Echo in shell scripts is more powerful than most people think.

This guide covers real usage logging, debugging, variables, and automation 👇

https://www.linuxteck.com/learn-to-use-echo-in-shell-scripts/

#Linux #Bash #ShellScripting #DevOps #LinuxTeck

This is old news to anyone with actual command-line skills, but it saved me today when doing a Blender render that kept crashing. I normally render from the command line because it means I can keep posting toots, er, I mean working productively for my employer in the foreground while it's rendering, and because it's usually faster (especially if you can run multiple instances).
Since I set up my scene to render an image sequence with overwriting turned off I can restart the render each time and pick up where it left off. But because command line, I can automate that process. In zsh (it will probably work on Bash or other shells I dunno) I do:
`blender -b '/path/to/my/project.blend' -a; while [[ $? != 0 ]]; do; echo "!!!! Oh bollocks !!!!"; blender -b '/path/to/my/project.blend' -a; done`
The guts of it is the `while` loop. This will loop as long as `$?` is not equal to 0. `$?` is a variable that holds the result of the previous operation, which is 0 if the previous operation succeeds. So if blender crashes it returns some non-zero return code, and the loop starts it up again.
For info on rendering from the command line: https://docs.blender.org/manual/en/latest/advanced/command_line/render.html
#blender #ShellScripting #CommandLine

---EDIT----
Check the replies for a more terse and elegant way to do this.
Also, here's a screenie of it in action, you can see it crashing and then starting again. This is on OSX so there's a dialog box that pops up, luckily the shell ignores the user's rsponse and continues anyway.
1/2

Wrote a #shell function without using ls inside of $( ), so my inner @mirabilos won't harass me. XD

Hmm, seems ${foo,,} for lower case conversion is #bash-only. I wonder if I should use tr instead.

#Unix #UnixShell #ShellScript #ShellScripting

Zsh: select generated files with (om[1]) glob qualifiers - Adam Johnson
https://adamj.eu/tech/2026/01/27/zsh-om1-glob-qualifiers/

#zsh #shellscripting

Some really neat tricks here in this Shell Tricks blog post by https://burningboard.net/@Larvitz -- thanks Larvitz!

I knew of most of them, but am glad to have now learned of:

1. "fc" to edit the previous command in your editor of choice
2. "**" (globstar) for recursive searching instead of needing to use find (or ls -R)
3. That "esc-." is repeatable to go back further than just the previous command's last arg. I use that all the time, but never thought to hit it more than once!

https://blog.hofstede.it/shell-tricks-that-actually-make-life-easier-and-save-your-sanity/

#shell #ShellTricks #shellscripting