Server Commands/GLINE
m |
|||
| Line 1: | Line 1: | ||
<pre>GLINE [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]</pre> | <pre>GLINE [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]</pre> | ||
| - | |||
| - | + | G-lines are fairly complicated. A G-line can be active or inactive, either locally or globally. It can be a purely local G-line, or global. It could be based on an IP address or on hostname. In short, there are many variations on the basic G-line. Worse, there is also the concept of a "bad channel", or BADCHAN, that has been tacked onto the G-line subsystem, when, in all honesty, should have been a separate command in the first place. | |
| + | On DareNET, IRC operators cannot use the "!" prefix, or set global G-lines via the command GLINE command. Trying to do so will result in the server rejecting the command. Instead, OperServ should be used to set wide and/or global G-lines. | ||
| + | |||
| + | If <mask> is not given, or if it is not prefixed by "+" or "-", a list of G-lines will be returned. If the "+" or "-" prefixes are used, the <expiration> and <reason> parameters must be given, even if the G-line already exists. On DareNET, if you do specify <target>, it must be the local server; otherwise, it will be rejected. If left blank, it is implied to be a local G-line. If the G-line currently exists, a prefix of "+" will cause an inactive G-line to be activated, whereas a prefix of "-" will cause an active G-line to be deactivated. If an attempt is made to modify a G-line set by a U-lined services, such as OperServ, the change will be forced to be local. The <type> argument can be used to G-line user realnames (gcos) by using $R. The expiration can be specified either in seconds or as a formatted time (e.g. 2d5m3s). | ||
[[Server Commands|(Return to Main listing of Server Commands)]] | [[Server Commands|(Return to Main listing of Server Commands)]] | ||
Revision as of 18:19, 24 September 2008
GLINE [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]
G-lines are fairly complicated. A G-line can be active or inactive, either locally or globally. It can be a purely local G-line, or global. It could be based on an IP address or on hostname. In short, there are many variations on the basic G-line. Worse, there is also the concept of a "bad channel", or BADCHAN, that has been tacked onto the G-line subsystem, when, in all honesty, should have been a separate command in the first place.
On DareNET, IRC operators cannot use the "!" prefix, or set global G-lines via the command GLINE command. Trying to do so will result in the server rejecting the command. Instead, OperServ should be used to set wide and/or global G-lines.
If <mask> is not given, or if it is not prefixed by "+" or "-", a list of G-lines will be returned. If the "+" or "-" prefixes are used, the <expiration> and <reason> parameters must be given, even if the G-line already exists. On DareNET, if you do specify <target>, it must be the local server; otherwise, it will be rejected. If left blank, it is implied to be a local G-line. If the G-line currently exists, a prefix of "+" will cause an inactive G-line to be activated, whereas a prefix of "-" will cause an active G-line to be deactivated. If an attempt is made to modify a G-line set by a U-lined services, such as OperServ, the change will be forced to be local. The <type> argument can be used to G-line user realnames (gcos) by using $R. The expiration can be specified either in seconds or as a formatted time (e.g. 2d5m3s).
