|
UNIX Hints & Hacks |
 |
|||||||||||||||||||||||||||||||
|
Chapter 10: System Administration: The Occupation |
|
|||||||||||||||||||||||||||||||
|
The basic duties and responsibilities were covered previously in section 10.1. However, there are more functions of system administrators that sometimes go overlooked. Following are some functions that administrators should have technical knowledge of depending on their level of expertise.
Install and configure systems: An administrator needs to know how to install or upgrade the operating system off the installation base CDs or floppy disks, depending on the flavor of UNIX being installed. An understanding of the naming conventions for the disk drive devices that can be configured, formatted, and labeled and the various ways it should be partitioned for that particular system is required. Knowing what software can and should be installed on a system, and where it will be installed, is vital to a successful installation of the operating system.
Set up multiple systems: UNIX administrators should be familiar with establishing connectivity with multiple systems either on the same subnet or over multiple subnets. In larger environments with a centralized file server, they should be able configure the servers' shared areas over NFS mount points to all the multiple systems in the environment if needed. They need to understand the concepts of NIS to provide users in the environment an easy and consistent way to log in to any system on the network and access their files.
Programming and porting: There is a lot of software available free on the Internet without precompiled binaries. The ability to port the source code to any of the systems in the environment is always needed. Many companies enjoy creating homegrown software, and when a new version of the operating system is released or new platforms are purchased, the software has to be ported by the UNIX administrator. As an administrator, you're not always responsible for all the software loaded on the system. That responsibility is sometimes left to management, or it might depend on the amount of resources available or on how much help users need.
Networking: Administrators need to be well versed in the different type of network configurations. There aren't too many systems independent of a network; although there are incidents where this still does occur. Whether a couple of systems are being configured on an isolated network or the environment is configured with a large number of systems on a complex LAN and WAN, an administrator must be able to exhibit clear knowledge of establishing connectivity between various systems over several type of networks. In some rare cases, systems are not configurable with the systems administrator tools, such as SAM (on HP) or smit (on IBM). When this occurs, the administrator must be able to configure the network manually and know where to hard code the changes into the appropriate files so the network activates when the system boots.
Security: Beginning at the intermediate level, administrators should show signs of interest and concern about security on the systems they administrate. Intrusion detection, protection, and auditing tools should get put into place. It is important, by this time, to begin learning the fundamentals of locking a UNIX system down and knowing which system files are involved. The installation process of some of the high-profile public domain UNIX security tools--cops, crack, Tripwire, Tiger, Gabriel, TCP/Wrappers, Satan, and others--should start to become common knowledge by this point.
Educator: Administrators have always exhibited the need to share knowledge and experience with others. Whether sharing information in classes and lectures, or training individual users or operators, administrators need to be able to convey information about basic and complex UNIX topics, commands, the general working environment, and applications that run within the environment. They must communicate in clear and understandable terms that the audience will comprehend.
Documentation: Administrators of all levels need to be able to communicate in writing, clearly. Various forms of documentation needs to be put together. Documentation can consist of procedures, policies, status reports, and other forms of information documented for control purposes. System utilization reports, software installation procedures, security policies, the location of backup tapes in a library, and instructions for running applications, are some of the things that administrators have to document. Many of the tasks being documented are placed into Web pages so that they can be viewed anytime by anyone. Administrators now have the ability create automation routines that manage documents on-the-fly and automatically generate Web pages for the internal intranet at the company.
Customer support: Much of UNIX administration involves customer support and dealing with users. Administrators will sometimes have to handle more than one user's problem at a time and make quick priority judgment calls while keeping the user happy and providing them with support. Administrator's users are their customers, and they cannot forget the old adage, "The customer is always right."
High ethical standards: As UNIX administrators you are expected to uphold the highest of ethical standards no matter who is involved. Administrators may be asked by management and friends to do unethical tasks when they have felt that their own positions where at risk. Administrators must stand on their principles and deny management and friends unsavory favors. I have not heard of an incident yet, where an administrator was fired for not upholding their ethical standards. Administrators have the potential of seeing many emails that go against policy and files in various directories that also may break corporate policy. Administrators can check with the human resources department within their organization for a policy on corporate ethics. Almost all companies have literature available on this subject.
Be a scavenger: Administrators must be scavengers. Budgets are usually tight and accessories and peripherals are difficult for administrators to acquire. They need to always be on the lookout for SCSI cables, networking equipment, external devices, spare memory, tapes, and anything else that may be lying around. They should always have a file or storage cabinet of some type to store the collected equipment. Trust no one but other UNIX administrators with your equipment, or you will never see it again.
Work long hours: UNIX administrators rarely work a 40-hour week. Most administrators work in excess of 40 hours a week; it is almost expected by management and other administrators. Here is a useful hint that may help you get that bonus or raise. Most time cards and electronic time tracking systems will have a slot for excess time. This is the amount of excess time (or overtime) you have given the company for which you get nothing in return. Mark this time whenever and wherever possible.
Many employers don't want the space marked, but push the point as far as possible. If you cannot use the space, track your own time. When you are up for an increase or bonus, ask to have your excess time added into your employee file.
Many senior managers, directors, and VPs, don't get to know you personally. Sometimes you are a number beside a figure that tells them how much they have to pay you out of their budget. When it comes time for bonuses and merit increases (raises), make sure they review your entire job performance including work habits, sick leave, vacations taken, and in many cases the amount of excess time you put into the company if you mark it. If they see go above and beyond the call of duty for the company you may just get that raise or bonus.
|
UNIX Hints & Hacks |
|
|||||||||||||||||||||||||||||||
|
Chapter 10: System Administration: The Occupation |
|
|||||||||||||||||||||||||||||||
|
© Copyright Macmillan USA. All rights reserved.
