Skip to main content

Musings on System Administration

I was reading an article discussing forensic preparation for computer systems. Some of the
stuff in there I knew the general theory of, but not the specifics of how to perform. As I
thought about it, it occurred to me that Systems Administration is such a vast field. There
is no way I can know all of this stuff. I made a list of the software and operating systems

I currently manage. They include:
- Windows Server 2003, Standard and Enterprise
- Exchange 2003
- Windows XP
- Windows Vista
- Windows 2000
- Ubuntu Linux
- OpenSuSE Linux
- Mac OSX (10.3 and 10.4)
- Solaris 8
- SQL 2005
- Various specialised software for the transport industry

I have specific knowledge on some of this, broad knowledge on all of it, and always think "There's so much I *don't* know". It gets a bit down heartening sometimes. For one thing - I
have no clue about SQL 2005 and I need to make it work with another bit of software. All
complicated and nothing straightforward. Irritating doesn't begin to explain it. As to the
Microsoft Software - because of it's prevalence throughout the world, there is a lot of
online information available. Likewise with Linux - it's incredibly rare to encounter a problem someone else hasn't already come up against.

So how to function within such an environment? Understanding I think is the key. The more
you understand about the process, the easier it is to figure things out. To my reckoning, understanding the "why" of how things work makes the job of learning new things fast to fix
problems much easier. For beginning sysadmins it's probably the most important thing. That
and curiosity. I'm always interested in learning about new things and trying new stuff out. Having sufficient hardware to indulge in this obsession doesn't hurt either. If you can't have all new stuff - second hand stuff is a good way to play.

Comments

Popular posts from this blog

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( www.openkm.com ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin

Traffic Monitoring using Ubuntu Linux, ntop, iftop and bridging

This is an update of an older post, as the utilities change, so has this concept of a cheap network spike - I use it to troubleshoot network issues, usually between a router and the network to understand what traffic is going where. The concept involves a transparent bridge between two network interface cards, and then looking at that traffic with a variety of tools to determine network traffic specifics. Most recently I used one to determine if a 4MB SDSL connection was saturated or not. It turned out the router was incorrectly configured and the connection had a maximum usage under 100Kb/s (!) At $1600 / month it's probably important to get this right - especially when the client was considering upgrading to a faster (and more expensive) link based on their DSL provider's advice. Hardware requirements: I'm using an old Dell Vostro desktop PC with a dual gigabit NIC in it - low profile and fits into the box nicely. Added a bit of extra RAM and a decent disk and that&