Server Commands/GLINE
| Command Token: GL |
GLINE [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]
G-lines themselves 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 can be based on an IP address, hostname or even gcos. 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 subsyetem, when, in all honesty, should have been a separate command in the first place.
! prefix
The "!" prefix has been disabled on DareNET. It's used to forcefully place G-lines that otherwise would be denied by the server for being "too wide." If you need to set wide G-lines, use OperServ instead, or contact the Abuse Team <abuse@darenet.org>.
If <mask> is not given, or it is not prefixed by "+" or "-", a list of G-lines will be returned. If the "+" or "-" prefixes are used, then the <expiration> and <reason> parameters must also be given, even if the G-line already exists.
If <target> is specified, then it MUST match the local server (e.g. the server you are on); otherwise it is implied. By default, the ability to set remote or global G-lines has been disabled for all IRC operators. Instead, OperServ should be used instead. However, such permissions can be granted through OperServ by a network administrator, but this is rarely done.
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).
