File: services.txt

package info (click to toggle)
ircd-ratbox 3.0.6.dfsg-2%2Bsqueeze1
  • links: PTS
  • area: main
  • in suites: squeeze
  • size: 12,632 kB
  • ctags: 11,261
  • sloc: ansic: 123,099; sh: 26,517; makefile: 775; yacc: 258; lex: 246; perl: 93
file content (55 lines) | stat: -rw-r--r-- 1,928 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
- ratbox-services compatibility documentation - Lee H <lee -at- leeh.co.uk> -
-----------------------------------------------------------------------------

Compatibility with ratbox-services can be enabled by passing the
'--enable-services' flag to configure.  It will add the following features
to ircd:

- Channel mode +r -

   A simple mode taking no parameters, will require users are logged in
   with user services before they may join the channel.

   Gives numeric 477 to users who arent logged in:
   :<server> 477 <nick> <channel> :Cannot join channel (+r)

- service block to ircd.conf -

   Ability to specify the names of services servers in ircd.conf:
   service {
       name = "services.ircd-ratbox.org";
       name = "backup-services.ircd-ratbox.org";
   };

   These must be specified for certain features to work.  You may specify as
   many name entries as you wish, however you must define only one service
   block.

   Entries will be listed in stats U with the flag 's'.

- Services protection -

   Services will be protected from being deopped or kicked from a channel.

- Username tracking through netsplits -

   When users are logged in, the username they are logged in with will be
   preserved on a netsplit, so users will not have to relogin when the
   network merges together.

- Username given on WHOIS -

   When users are logged in, WHOIS will also give numeric 330:
   :<server> 330 <yournick> <targetnick> <loginname> :is logged in as

   Note this needs to be a remote whois to work when the target is
   on a different server.

- Forced nick change -

   When using nickname services and a client requests they regain a
   nickname, services can perform a forced nick change on the client.
   This forcibly changes the clients nickname to the one they requested
   they regain, ensuring they can always regain their nickname.

# $Id: services.txt 23020 2006-09-01 18:20:19Z androsyn $