This is an old revision of the document!
system administration policies
To the extent feasible, system administration policies applicable
to this "box" (host) are to be documented here.
Note that occasionally there will be some items more appropriately
documented elsewhere. E.g. security sensitive information that
shouldn't be openly readable to the Internet, or items that may be
important to have access to when the wiki isn't available (e.g. critical
maintenance related information).
In general, items which shouldn't be documented here on this wiki but
should be documented in local files under
file:/home/admin/ - or at least referenced from there.
To the extent feasible, this document should cover current policy,
"rules of the road", etc. To the extent it's covered, historical,
outdated, superseded, etc.
information should be covered separately (and to the extent feasible,
presented in a manner unlikely to cause confusion with current policy
and "rules of the road", etc.)
There are multiple objectives for this system. At least at times,
these may appear to conflict. This list is intended to identify
key objectives, and in the case of conflict or potential conflicts,
their priority (or at least approximate priority), with highest priority
(most important) first.
High availability server
- to the extent feasible, this system should be treated as a server intended to be of rather to quite high availability. E.g. groups (such as SF-LUG
) are or may be rather to quite dependent upon its availability, and generally would prefer the system be up and available as much as feasible.
Downtime and maintenance (system outages)
- to the extent feasible, when such outages are necessary or appropriate, they should be targeted to off-peak hours (usage logs may provide useful guidelines as to what days/times would best meet "off-peak" criteria), and should be scheduled in advance and with appropriate outage notification
to support command-line activities of sf-lug members
provide an educational playground for sf-lug members who want to explore learning LINUX
to support web pages for anyone, sf-lug member or not
a guide for studying to pass the Red Hat Certified Technician (RHCT) and the Red Hat Certified Engineer (RHCE) tests
dos, dont's, and how tos
significant changes to policy, use of system
, concerns/questions, etc. - such issues (at least presently) should generally be discussed to "resolution" on the SF-LUG list
avoiding configuration/usage conflict - to the extent feasible, items should be appropriately identified and/or located, as applicable, to avoid conflicts and confusion. E.g. for usages which may not be absolutely primary to the box (e.g. BALUG) configurations should be clearly identified (e.g. /etc/named-balug.conf, /etc/init.d/named-balug) and/or in appropriate areas (e.g. /home/balug).