This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
policies:operguidelines [2009/10/01 02:51] rubin Clean up and clarify the rules |
policies:operguidelines [2011/04/11 08:32] hacker_dan |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Network Operator Guidelines====== | ====== Network Operator Guidelines====== | ||
- | **A note to our users**: These rules act as a guide for us, your network operators and administrators, | + | **A note to our users**: These rules act as a guide for us, your network operators and administrators, |
===== Operator Guidelines ===== | ===== Operator Guidelines ===== | ||
Line 39: | Line 39: | ||
=== Other oper guidelines === | === Other oper guidelines === | ||
- | * Missing servers should be reconnected automatically by X3, which will try once an hour if they don't return immediately. Regardless, opers should try to connect them as well. The X3 command " | + | * Missing servers should be reconnected automatically by X3, which will try once an hour if they don't return immediately. Regardless, opers should try to connect them as well. The X3 command " |
* Improperly routed servers should NOT be rerouted unless the routing is causing problems on the network or a current hub needs to stop hubbing. Netsplits should be avoided at all times as they are a huge inconvenience to the users. Improperly routed servers will correct themselves over time - as they split X3 will reconnect them properly. | * Improperly routed servers should NOT be rerouted unless the routing is causing problems on the network or a current hub needs to stop hubbing. Netsplits should be avoided at all times as they are a huge inconvenience to the users. Improperly routed servers will correct themselves over time - as they split X3 will reconnect them properly. |