User Tools

Site Tools


system:system_administration_rules_of_the_road_this_box

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

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-29T20:59:18+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 33: Line 33:
   *support web pages and activities of users learning the Python programming language   *support web pages and activities of users learning the Python programming language
   *support other open-source focussed community groups   *support other open-source focussed community groups
-===dos, ​dont's, and how tos===+===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:   ***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     ***[[system:​change log]]** - relatively selective high-level change log
-    ***file:/​home/​admlin/​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** ​ - (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/​admlin/​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.+    ***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=== ===Code of Ethics===
system/system_administration_rules_of_the_road_this_box.txt · Last modified: 2018-09-03T04:13:22+0000 by michael_paoli