My 10 UNIX Command Line Mistakes – nixCraft
Posted by jpluimers on 2019/01/28
An interesting series of mistakes that anyone can make followed by a long thread of discussion with various people making mistakes on many operating systems:
My top 10 biggest UNIX / Linux command-line mistakes that cause some sort of down time. Try to avoid them.
[WayBack] My 10 UNIX Command Line Mistakes – nixCraft
…
Conclusion
All men make mistakes, but only wise men learn from their mistakes — Winston Churchill.
From all those mistakes I have learn that:
- You must keep a good set of backups. Test your backups regularly too.
- The clear choice for preserving all data of UNIX file systems is dump, which is only tool that guaranties recovery under all conditions. (see Torture-testing Backup and Archive Programs paper).
- Never use rsync with single backup directory. Create a snapshots using rsync or rsnapshots.
- Use CVS/git to store configuration files.
- Wait and read command line twice before hitting the dam [Enter] key.
- Use your well tested perl / shell scripts and open source configuration management software such as puppet, Ansible, Cfengine or Chef to configure all servers. This also applies to day today jobs such as creating the users and more.
Mistakes are the inevitable, so have you made any mistakes that have caused some sort of downtime? Please add them into the comments section below.
I didn’t know about rsnapshots, so I need to put some research in it, hence the links below.
Note that the rsnapshots documentation is a bit behind the source code, so if you look for the HOWTO, then you’ll get a 404. The old HOWTO is in a link below.
- [WayBack] rsnapshot | rsnapshot: rsync-based backup utility
- [WayBack] HOWTO is missing? · Issue #93 · rsnapshot/rsnapshot
- [WayBack] FAQ | rsnapshot
–jeroen
Via: [WayBack] Joe C. Hecht – Google+: Here are a few mistakes that I made while working at UNIX/Linux prompt.
The Wiert Corner - irregular stream of stuff 
Leave a comment