system:system_administration_rules_of_the_road_this_box
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
system:system_administration_rules_of_the_road_this_box [2007-04-24T06:03:19+0000] 198.144.194.236 |
system:system_administration_rules_of_the_road_this_box [2007-05-14T02:11:36+0000] 198.144.194.236 typo fixes |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====system administration policies==== | + | ====system administration policies / "rules of the road" (this box)==== |
| To the extent feasible, **system administration policies applicable | To the extent feasible, **system administration policies applicable | ||
| - | to this "box" (host) are to be documented here**. | + | to this "box" (host/system) are to be documented here**. |
| Note that **occasionally there will be some items more appropriately | Note that **occasionally there will be some items more appropriately | ||
| Line 27: | Line 27: | ||
| ***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 [[http://www.sf-lug.org/|SF-LUG]] and [[http://www.balug.org/|BALUG]]) 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. | ***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 [[http://www.sf-lug.org/|SF-LUG]] and [[http://www.balug.org/|BALUG]]) 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 [[system:appropriate outage notification]]. | ***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 [[system:appropriate outage notification]]. | ||
| - | *to support command-line activities of sf-lug members | + | *support command-line activities of users |
| - | *provide an educational playground for sf-lug members who want to explore learning LINUX | + | *provide an educational playground for users who want to explore using LINUX |
| - | *to support web pages for anyone, sf-lug member or not | + | *support web pages for users |
| - | *a guide for studying to pass the Red Hat Certified Technician (RHCT) and the Red Hat Certified Engineer (RHCE) tests | + | *support web pages and activities of a Red Hat Certification study group |
| - | + | *support web pages and activities of users learning the Python programming language | |
| - | ===dos, dont's, and how tos=== | + | *support other open-source focussed community groups |
| + | ===dos, don'ts, 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 [[http://linuxmafia.com/mailman/listinfo/sf-lug|SF-LUG list]] | ***significant changes to policy, use of system**, concerns/questions, etc. - such issues (at least presently) should generally be discussed to "resolution" on the [[http://linuxmafia.com/mailman/listinfo/sf-lug|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). | ***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). | ||
| + | ***logging** - things/events/changes should be suitably and appropriately logged, and in appropriate location(s). This is not only generally considered "best practice", but it is particularly important when multiple persons are involved (e.g. with systems administration) on a host - such as the case with this host. There is not only the logging done by software itself (and via its configuration), but also appropriate (mostly) human generated log entries and/or details. Exactly how, where, and what, should be logged, may "evolve" over time (and with discussion and seeing what does/doesn't work so well for different stuff). At present, there are at least these, and their apparent current usage: | ||
| + | ***[[system:change log]]** - relatively selective high-level change log | ||
| + | ***file:/home/admin/log** - (up to) rather detailed chronological logging potentially including anything that might be worthy of noting/recording. It's also readable by anyone via the Internet (accessible as [[http://www.sf-lug.com/log.txt]]), so only items suitable for being that openly exposed should be placed there. | ||
| + | ***file:/home/admin/log.secure** - similar to the above, for items that should have quite minimal exposure (limited to local superuser (UID 0, a.k.a. "root") access. | ||
| + | ***documenting**/**documentation** - as feasible and appropriate, things should be documented (and/or logged). This is particularly noteworthy/important given both the number of folks that do or may work on this system, and also many of the objectives of the system (e.g. learning/teaching). | ||
| + | ***IP addresses**: see: **[[system:ip_addresses|IP addresses]]** | ||
| + | ***BALUG webserver**: see: **[[BALUG webserver]]** | ||
| + | ***BALUG DNS server**: see: **[[BALUG DNS]]** | ||
| + | |||
| + | ===Code of Ethics=== | ||
| + | Access to and use of the system should follow appropriate code of ethics, e.g. | ||
| + | the LOPSA/SAGE/USENIX code of ethics: | ||
| + | *[[http://www.sage.org/ethics/ethics.html|the LOPSA/SAGE/USENIX Code of Ethics]] [[http://www.usenix.org/|(USENIX]]/[[http://www.sage.org/|SAGE)]] | ||
| + | *[[http://lopsa.org/CodeOfEthics|the LOPSA/SAGE/USENIX Code of Ethics]] [[http://lopsa.org/|(LOPSA)]] | ||
| + | |||
| + | ===policies history=== | ||
| + | [[system:policies history]] | ||
system/system_administration_rules_of_the_road_this_box.txt · Last modified: 2018-09-03T04:13:22+0000 by michael_paoli
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC0 1.0 Universal
