Comments on: Three Sysadmin Rules You Can’t (And Shouldn’t) Break

By: Hellmut Weber

Hellmut Weber — Mon, 02 Jan 2012 23:52:07 +0000

IMHO an equally important rule for the sysadmin is:

Document every change you make on your system!

Clearly for every change made the reason for the change should be mentioned, and a reference to test results for the change should be given.
Probably a hint how to revoke the chance could be helpful, IF this is possible.

Best regards

Hellmut

By: Pat

Pat — Sun, 23 Oct 2011 22:13:45 +0000

Here’s my own rules.
1.) Always check the logs.
2.) Google is your friend.
3.) Think twice before pressing enter.
4.) Don’t try to fix things if aren’t broken. (Most if not all always try to do things in their server and eventually end up messing it.)

By: 12 Reasons Why Every Linux System Administrator Should be Lazy

12 Reasons Why Every Linux System Administrator Should be Lazy — Wed, 20 Jul 2011 06:05:07 +0000

[...] restore from the backup, and get back to whatever lazy stuff he was doing before. This is also the rule#1 in the three sysadmin rules that you shouldn’t [...]

By: Solaria

Solaria — Sat, 25 Jun 2011 15:57:57 +0000

Rule #2: GUI’s are great, but what if the GUI isn’t available? As sysadm you will be called on to fix the system when major parts have failed… your only interface may be the CLI while you make repairs. The rule is “Always have an alternate path into the machine”. If you can’t connect to Xwindows, maybe you can SSH or RSH from another server, or use the Remote System Console (ILO, RSC, etc) through a remote KVM or serial switch. I’ve had to restart system processes using an SSH client from my cell phone, while parked in a supermarket parking lot. The CLI is always available, more reliable, faster, easier to document, etc… Sort of like using the “vi” editor: other editors may have an easier UI, but vi is always available.

For Windows, I install Cygwin SSHD on each server. Not quite the same as Linux, but much of the admin-ing can be done from the CLI, and automated.

By: srinivas

srinivas — Fri, 17 Jun 2011 11:24:09 +0000

Hi Nataraj

Rules are very good . I don’t think there is an article on these three by you . It would be great if u can provide it as i am new to this Linux domain

By: Erik

Erik — Sun, 12 Jun 2011 20:57:11 +0000

hi,

yes what happend to the “only be root when it is absolutely necessary” basic but important one…

By: Doug Meier

Doug Meier — Thu, 19 May 2011 15:20:07 +0000

lazy sys admin is great IF lazy sys admin documents his automated processes and trains junior lazy sys admin to lazily manage them. otherwise lazy sys admin becomes a point of failure for the organization.

By: vikas maske

vikas maske — Fri, 13 May 2011 05:38:53 +0000

This is really really nice information.

By: Roy

Roy — Fri, 06 May 2011 18:50:46 +0000

Agree with 1 and 2.
automation not only makes you lazy but it also make you forget the less used procedures/commands.

Also, I would add a 4th one – Documentation. A good sysadmin will document everything so that another sysadmin (or the management) can understand what the previous admin has done.

By: skape

skape — Fri, 25 Feb 2011 17:50:41 +0000

I agree with the rules, the third one is my very nature, I admit I’m lazy! Let the machine do that returning taks that are boring, and i’m certailnly messing it up because I’m human.

but there is a 4th rule that I hate but I’ve suffered because someelse didn’t followed it.

Document everything! You may be a single point of failure in the system. The people that step in to keep things going will have a hard time figuring everything out.