stats
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | stats [2006/08/29 16:08] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | #$EPIC: stats.txt,v 1.2 2006/08/20 16:57:01 sthalik Exp $ | ||
| + | ======Synopsis: | ||
| + | __stats__ < | ||
| + | |||
| + | ======Description: | ||
| + | **IMPORTANT**: | ||
| + | before trying to use this command. | ||
| + | |||
| + | This asks the server for general purpose information. | ||
| + | data you can request is statistical in nature, but not most of it. | ||
| + | The most common data to request is information about the server' | ||
| + | configuration. | ||
| + | |||
| + | A " | ||
| + | on every server on the network. | ||
| + | operator; he appears as an operator only on his own server. | ||
| + | |||
| + | On ircnet servers, an " | ||
| + | client connections. | ||
| + | automatically bestows upon them user mode +r, which restricts what they | ||
| + | can do. See the [[MODE]] help page for more information. | ||
| + | |||
| + | ======Options: | ||
| + | __STATS__ options are not preceded by a hyphen! | ||
| + | |||
| + | |c |C/N lines: A list of peer servers who may **C**onnect here. | | ||
| + | |h |H/L lines: For each peer, whether they are a **H**ub or Leaf server. | ||
| + | |k |K lines: A list of client userhosts who are auto-**k**illed (banned). | ||
| + | |i |I lines: A list of permitted **I**ncoming client connections. | ||
| + | |l | ||
| + | |m | ||
| + | |o |O lines: A list of clients permitted to become **O**perators. | ||
| + | |u | ||
| + | |y |Y lines: Special parameters governing each client and server connection. | ||
| + | |p | ||
| + | |||
| + | ======Privacy: | ||
| + | __STATS__ usage is reported to opers on many servers. On servers which | ||
| + | report STATS queries, you may be questioned about the purposed of | ||
| + | these queries, or, in some cases, immediately banned (K-lined) from | ||
| + | the server. Reporting of __STATS__ queries originated at a time where | ||
| + | __STATS__ was regularly used to flood servers. Most servers now | ||
| + | ratelimit or otherwise restrict such queries, however many still report | ||
| + | them to opers. | ||
| + | |||
| + | ======Restrictions: | ||
| + | For many reasons, the use of this command is now restricted in some | ||
| + | way on most servers. Information about how a server is configured | ||
| + | can (and often is) used to abuse the server. __STATS__ queries often | ||
| + | generate a lot of output, so they were used in many cases to make | ||
| + | a server flood itself. | ||
| + | |||
| + | Restrictions you may encounter include: | ||
| + | - Some or all queries restricted to server operators. | ||
| + | - Some output restricted to server operators. | ||
| + | - Rate limiting. | ||
| + | - Restrictions on " | ||
| + | - Notification to server operators. (see Privacy section above). | ||
| + | |||
| + | ======Other Notes: | ||
| + | Many networks and server now support __STATS__ queries beyond those listed | ||
| + | here, however they are typically limited to server operators. | ||
stats.txt · Last modified: 2006/08/29 16:08 by 127.0.0.1
