----- Original Message ----- > Those of you not in #lopsa (shame on you!) are missing a great > thread... > > Great typos, the best way to destroy a system, unexpected command > line results...
So many 'learning opportunities' over the years... Using Ctrl-Alt-Del to lock you NT4 console is a good thing, using Ctrl-Alt-Del to try and lock your OS/2 Lotus Notes server *not* a good idea. Before OutOfOffice notices were all the rage, I created one for the admin account of our Lotus Notes server (when email was an addon feature). It would CC me and everyone else that was on the original email that the account was not monitored. Well I didn't keep that in mind when I then set the same script on my own account, and CC'd the admin account for some reason. I went home, and an hour later realized that it shouldn't take longer than 30m to replicate email. By time I finally got into my database I saw that a mailing list I was on sent a note, which sent back to the list, which was delivered to me. I think it got to the point where the emails were growing 5m/minute before I finally just turned off the server... Lots of hate mail that day. Hmm... lots of stray notes processes on this AIX server. I'll just use killall. Hey.. where the console go? I had to setup a redundant set of servers at a different data center. When rsyncing a bunch of files I noticed a directory in /var that had nothing but links in it. It looked to be part of the order processing system, but all the config files pointed to other directories. Asked my manager if they were needed and he couldn't figure out why they were there either. So I deleted that directory (after getting permission) and I hear the sales team let out a scream (as if millions of voices all screamed out...). We learned relatively quickly that the order system used that directory as a listing of all of the files that made up the site. It then used them as the basis for the security system. If the file doesn't exist, then no one was allowed access. Oh and whoever coded it felt that if you delete the file, then no reason to keep around the old permissions either. Same company, same project, still moving files. Apparently the way the EDI system was setup was to look at the date of the files to determine if it needed to send them to the vendor. I forgot the archive bit. It took weeks for them to catch and clear all of the resent orders, since only one of the many vendors was smart enough to look for resent orders. Setting up Database replication is a good idea. Using a database copy that is a day old on an active eCommerce website to seed the master database is a bad idea. (I still don't remember why i did it that way). Since the previous three examples happened in the span of a month, I have become a helluva lot more careful about how I plan and do things... and learned how to update my resume quickly ;) all of my rm *.* experience happened on the first day I installed Linux. I reinstalled Slackware so many times that day, i could almost do it blindfolded. _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
