May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Side effects/unintended consequences of multiple sysadmin working on the same box

News Sysadmin Horror Stories Recommended Links dirhist utility Creative uses of rm Mistakes made because of the differences between various Unix/Linux flavors Missing backup horror stories Pure stupidity
Locking yourself out Premature or misguided optimization Reboot Blunders  Performing the operation on a wrong server Executing command in a wrong directory Side effects of performing operations on home or application directories Typos in the commands with disastrous consequences Side effects of patching
Multiple sysadmin working on the same box Side effects of patching of the customized server Ownership changing blunders Dot-star-errors and regular expressions blunders Excessive zeal in improving security of the system Unintended consequences of automatic system maintenance scripts Lack of testing complex, potentially destructive, commands before execution of production box Abuse of privileges
Safe-rm Workaholism and Burnout Coping with the toxic stress in IT environment The Unix Hater’s Handbook Tips Horror stories History Humor Etc

The sysadmins I've worked are hardened guys used to dealing with  wannabes who forget that they are not the only users and that other users requests are equally important.  But sometimes the danger lurk in completely different area and this is your colleagues. I am not talking about backstabbing which also happens, I am taking about catastrophic errors. Often the second admin is the person who is running an application on this server and who does not know Unix all that well. If you allow such a person to administer your server you better be willing to train him/her.

dirhist utility can create history of changes in viral system directories and inform administrator daily if change in viral files or directories occurred. That prevents mishaps due to not misunderstanding or incomplete information about changes.

Sometimes after doing something stupid on the box people try to hide that complicating recovery.  That works both way: if you did such thing it's better to come forward.

Beware side effects connected with the customarization of root account including adding aliases. Think twice before changing the way root account configured if you are not the only person working on the box.  Using Subversion or other CMS is also highly recommended.

Here is one interesting example:

userdel Command

The file /etc/deluser.conf 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. I just wanted to remove the user account and I end up deleting everything (note -r was activated via deluser.conf):
userdel foo

Dr. Nikolai Bezroukov

Top Visited
Past week
Past month


Old News ;-)

Advice and tips for a junior sysadmin straight out of college

Server Fault
I've recently graduated and have got a job at a fast-growing dedicated/VPS hosting company as a junior sysadmin.

I'd like to know any tips or advice you more senior sysadmins have, e.g. what mistakes did you make when you were younger, certification, how to stay organised.

My best piece of advice is to remember ignorance is not a sin. You don't know everything, nobody does. Read the documentation, ask for help. It is far better to spend some time and possibly a few shreds of credibility with your peers to find learn before you screw up, than to leap in and really mess something up. Everybody screws up sometime. Just don't be the one who screws up because they didn't RTFM or ask around first.
link|flag answered Jun 19 '09 at 20:27

Laura Thomas

Yup, assume you know nothing. Read, and read some more, then ask targeted questions. Try to document systems from the point of view of a novice. This will help you understand how everything is set up and provide something useful for the next junior sysadmin - when you stop being the new boy. Over the course of the next 6 months you're likely to learn more than you did in college. – Geoff Jun 19 '09 at 20:32

I love this advice. It will also help you avoid driving your technically-competent customers up the wall. I have no problem with support staff who don't know the answer to something and are willing to admit it and bring in a senior tech. It's the ones who insist that they do know, when they clearly don't, who need to find new jobs. – Ben Dunlap Jun 19 '09 at 20:41
I agree with Laura here. Not knowing anything is where all of us started, and if we were honest where we all still are. If you approach with humility, you will be just fine. – Matt Jun 19 '09 at

And "assume you know nothing" is excellent advice also. In fact that's probably the only assumption you should ever make about any technical problem. The road to solving just about every really knotty problem I've ever encountered has begun with me asking myself, "what am I assuming here?" – Ben Dunlap Jun 19 '09 at 20:43
@Matt "if we were honest where we all still are" -- I'm not totally on-board with that. Sure, relative to "knowing everything about everything" we all know nothing. But some people really are experts in certain areas and they know it and that's fine. I think humility, in this context, is ultimately about recognizing what you know and what you don't. – Ben Dunlap Jun 19 '09 at 20:46

Recommended Links

Google matched content

Softpanorama Recommended

Top articles




Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy


War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes


Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law


Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2021 by Softpanorama Society. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: November 05, 2020