Hostname Public Network Interface Shutdown Within minutes I received an alert message on both mobile and email. Accidentally Changed Hostname and Triggered False AlarmĪccidentally changed the current hostname (I wanted to see current hostname settings) for one of our cluster node. I had sym links for my web server docroot (/home/httpd/http was symlinked to /To save disk space, I ran rm -rf on http directory. Similarly I end up running rsync command and deleted all new files by overwriting files from backup set (now I have switched to rsnapshot)Īgain, I had no backup. I end up deleting entire backup (note -c switch instead of -x): I had only one backup copy of my QT project and I just wanted to get a directory called functions. mkzone > /var/named/chroot/etc/nf Destroyed Working Backups with Tar and Rsync (personal backups) I wanted to append a new zone to /var/named/chroot/etc/nf file., but end up running: As root I killed all process, this was our main Oracle db box: On Linux killall command kill processes by name (killall httpd). I just wanted to remove the user account and I end up deleting everything (note -r was activated via nf): The file /etc/nf was configured to remove the home directory (it was done by previous sys admin and it was my first day at work) and mail spool of the user to be removed. They say, “Failure is the key to success each mistake teaches us something.” I hope you will learn something from my 10 Linux or Unix command line mistakes as well as the comments posted below by my readers.
A list of my 10 UNIX command line mistakes
0 kommentar(er)
