ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/svn/vendor/ircservices-5.1.24/docs/5.html
Revision: 3389
Committed: Fri Apr 25 14:12:15 2014 UTC (9 years, 11 months ago) by michael
Content type: text/html
File size: 31631 byte(s)
Log Message:
- Imported ircservices-5.1.24

File Contents

# Content
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 <html>
3 <head>
4 <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
5 <title>IRC Services Manual - 5. Importing and exporting databases</title>
6 </head>
7
8 <body>
9 <a name=top></a>
10 <h1 align=center>IRC Services Manual</h1>
11
12 <h2 align=center>5. Importing and exporting databases</h2>
13
14 <p>5-1. <a href="#1">Exporting Services databases in XML format</a>
15 <br>5-2. <a href="#2">Importing (merging) data from an XML file</a>
16 <br>5-3. <a href="#3">Converting data from other Services-like programs</a>
17 <br>&nbsp;&nbsp;&nbsp;&nbsp;5-3-1. <a href="#3-1">Using the
18 <tt>convert-db</tt> program</a>
19 <br>&nbsp;&nbsp;&nbsp;&nbsp;5-3-2. <a href="#3-2">Notes on converting
20 databases from particular programs</a>
21
22 <p align=right><font size=-1><a href=4.html>Previous section: Services command reference</a> |
23 <a href=index.html>Table of Contents</a></font>
24
25 <p><hr>
26
27 <a name=1></a>
28 <h3>5-1. Exporting Services databases in XML format</h3>
29
30 <p>In order to facilitate processing of the Services databases by other
31 programs, Services provides the ability to export the databases in XML
32 format. This is accomplished through the <tt>misc/xml-export</tt> module
33 and, optionally, the <a href="3.html#6">HTTP server</a> built into
34 Services.
35
36 <p>The <tt>misc/xml-export</tt> module adds an extra command-line option,
37 <tt>-export</tt>, to Services. Since the command line is parsed before
38 Services connects to the network, the module must be specified in your
39 <tt>ircservices.conf</tt> file to enable this option. The option has the
40 format "<tt>-export</tt>" or "<tt>-export=<i>filename</i></tt>", where
41 <tt><i>filename</i></tt> is the name of the file to write the XML data to;
42 if it does not begin with a slash, it is taken to be relative to the
43 Services data directory (the directory containing the database and log
44 files). If <tt><i>filename</i></tt> is not given or is a single hyphen
45 ("<tt>-</tt>"), the data will be printed on standard output. When the
46 export completes, Services will terminate without connecting to the IRC
47 network. This action can be performed while another copy of Services is
48 running, but the output will not include changes made online since the
49 last time the databases were saved to disk. (It is also possible for the
50 running copy of Services to report a "data directory locked" error if it
51 tries to save the databases while the export operation is in progress.
52 This is harmless; you can force the databases to be written after the
53 export completes by using the OperServ
54 <a href="4.html#oper.update"><tt>UPDATE</tt></a> command, but do not use
55 the <tt>FORCE</tt> option while the export is still running as this may
56 result in corrupted database files.)
57
58 <p>Additionally, if the <tt>misc/xml-export</tt> module is loaded into
59 Services, the HTTP database access module (<tt>httpd/dbaccess</tt>) will
60 display an "XML database download" link. Clicking on the link will display
61 the XML data in your browser, which you can then save (for Firefox and
62 Internet Explorer, select "Save as..." or "Save page as..." from the
63 browser's File menu). Alternatively, you can download the link directly
64 without displaying it in your browser; in Firefox, hold the Alt key while
65 clicking on the link, and in Internet Explorer, right-click on the link and
66 select "Save target as..." from the pop-up menu.
67
68 <p>The format of the exported XML data is described in
69 <a href=b.html>Appendix B</a>.
70
71 <p><b>Notes:</b> Services will not respond to any network activity while you
72 are downloading the database. If you have a large database, this can make
73 Services appear to "freeze" with respect to the IRC network, and it may
74 even get disconnected from the network in extreme cases. Additionally, be
75 aware that the data may change after you have downloaded it; if you want to
76 avoid this, for example when exporting data to move it to another machine
77 or network, use the command-line option <tt>-export</tt> (after shutting
78 Services down) rather than the HTTP server interface.
79
80 <p><b>Note to Internet Explorer users:</b> Some versions of Internet
81 Explorer have a bug which can prevent the XML data from being displayed or
82 downloaded properly. If you have this problem, use another browser, or add
83 the following key to your registry using the Registry Editor
84 (<tt>regedit</tt>), as described in Microsoft Knowledge Base article
85 <a href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;q239750">Q239750</a>
86 <font size=-1>[<tt>support.microsoft.com</tt>]</font>:
87 <div align=center><table border=0>
88 <tr><td align=right>Key:<td>&nbsp;
89 <td><tt>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet&nbsp;Settings</tt>
90 <tr><td align=right>Value&nbsp;name:<td>&nbsp;<td><tt>IsTextPlainHonored</tt>
91 <tr><td align=right>Value&nbsp;type:<td>&nbsp;<td><tt>DWORD</tt>
92 <tr><td align=right>Value&nbsp;data:<td>&nbsp;<td><tt>HEX 0x1</tt>
93 </table></div>
94 Improper use of the Registry Editor can cause your system to malfunction,
95 so be careful when making any changes. You may also need to upgrade your
96 system files as described in the Knowledge Base article linked to above
97 if you are using Windows 95, Windows 98, or Windows NT 4.0.
98
99 <p align=right><font size="-1"><a href="#top">Back to top</a></font>
100
101 <p><hr>
102
103 <a name=2></a>
104 <h3>5-2. Importing (merging) data from an XML file</h3>
105
106 <p>Just as it can export data in XML format, Services can also read in XML
107 data and import (merge) it into its databases. Importing is handled by the
108 <tt>misc/xml-import</tt> module. Unlike exporting, however, importing
109 cannot be done via the HTTP server; it is always done through the command
110 line. For this reason, the <tt>misc/xml-import</tt> module must be loaded
111 at startup if it is to be used, rather than via an OperServ
112 <a href="4.html#oper.rehash"><tt>REHASH</tt></a> or a <tt>SIGHUP</tt>
113 signal.
114
115 <p>To import a set of data stored in XML format into Services, start
116 Services with the command-line option "<tt>-import=<i>filename</i></tt>",
117 where <tt><i>filename</i></tt> is the name of the file containing the data;
118 if the filename does not begin with a slash, it is taken to be relative to
119 the Services data directory. Services will parse the data file, and if no
120 errors are found, the data will be merged into Services' databases and the
121 program will terminate. If problems are found, they will be printed on
122 standard output and the databases will not be modified.
123
124 <p>Normally, if nickname or channel "collisions" occur&mdash;that is, if a
125 nickname or channel in the input data is already registered in Services'
126 databases&mdash;Services will skip over that nickname group or channel,
127 respectively. (For nicknames, the entire nickname group is skipped to
128 prevent cases where, for example, a user's secondary nick is available but
129 the primary nick is registered to someone else.) This behavior can be
130 modified by the
131 <a href="a.html#misc/xml-import.OnNicknameCollision"><tt>OnNicknameCollision</tt></a> and
132 <a href="a.html#misc/xml-import.OnChannelCollision"><tt>OnChannelCollision</tt></a>
133 options in <tt>modules.conf</tt>. Additionally, Services can be made to
134 output a list of all data imported by setting the
135 <a href="a.html#misc/xml-import.VerboseImport"><tt>VerboseImport</tt></a>
136 option (which is set in the example <tt>modules.conf</tt> provided with
137 Services).
138
139 <p>Note that the maximum user count and OperServ
140 <a href="4.html#oper.su"><tt>SU</tt></a> password will not be imported;
141 news items will not be imported unless the
142 <a href="a.html#misc/xml-import.ImportNews"><tt>ImportNews</tt></a> option
143 (in <tt>modules.conf</tt>) is set. Also, any autokills, autokill
144 exclusions, session limit exceptions, or S-lines which collide with those
145 in the database will be automatically skipped.
146
147 <p align=right><font size="-1"><a href="#top">Back to top</a></font>
148
149 <p><hr>
150
151 <a name=3></a>
152 <h3>5-3. Converting data from other Services-like programs</h3>
153
154 <a name=3-1></a>
155 <h4>5-3-1. Using the <tt>convert-db</tt> program</h4>
156
157 <p>For users of other Services-like programs who want to switch to IRC
158 Services, a program called <tt>convert-db</tt> is supplied to convert
159 databases used by such programs into XML data files, which can then be
160 imported into Services as described in <a href="#2">section 5-2</a> above.
161 This program is installed into the Services data directory
162 (<tt>/var/opt/ircservices</tt> for binary distributions,
163 <tt>/usr/local/lib/ircservices</tt> by default for source distributions).
164
165 <p>In its simplest form, <tt>convert-db</tt> takes the pathname of the
166 directory containing the database files to convert on the command line,
167 and writes the converted XML data to standard output. A typical invocation
168 might look like this:
169 <blockquote>
170 <tt>convert-db /usr/local/lib/<i>someprogram</i> &gt; <i>someprogram</i>.xml</tt>
171 </blockquote>
172 <tt>convert-db</tt> will look at the files in the directory given and
173 attempt to determine automatically what program created them; if this
174 succeeds, it will proceed to read in the database files and convert them to
175 XML. If <tt>convert-db</tt> cannot determine what program created the
176 files, you can tell it explicitly by adding a <tt>+<i>program-name</i></tt>
177 option in front of the path name (see the full syntax description below for
178 valid values for <tt><i>program-name</i></tt>).
179
180 <p>Note that not all features of all programs are supported by Services,
181 and some settings may be lost when you import data. See
182 <a href="#3-2">section 5-3-2</a> below for notes on particular programs,
183 and <a href="#2">section 5-2</a> for information on importing the converted
184 data into Services.
185
186 <p>The full syntax for <tt>convert-db</tt> is as follows:
187 <blockquote>
188 <tt>convert-db [-v] [+<i>program-name</i>] [<i>options</i></tt> . . . <tt>] <i>pathname</i></tt>
189 </blockquote>
190 The options and parameters are:
191 <ul>
192 <li><tt>-v</tt>: Display progress information as the data is converted.
193 <li><tt>+<i>program-name</i></tt>: Explicitly indicates what program was
194 used to create the data files. A list of possible
195 <tt><i>program-name</i></tt> values is given in table 5-1 below.
196 <tt><i>program-name</i></tt> values are not case sensitive.
197 <li><tt><i>options</i></tt>: Additional options specific to each type of
198 data file controlling details of the data conversion; see below.
199 <li><tt><i>pathname</i></tt>: Specifies the pathname of the directory
200 containing the database files.
201 </ul>
202
203 <div align=center>
204 <b>Table 5-1.</b> Values for <tt>+<i>program-name</i></tt> parameter to
205 <tt>convert-db</tt><br><br>
206 <table border=1>
207 <tr><th><tt><i>program-name</i></tt>
208 <th>Name&nbsp;of&nbsp;program
209 <th>Supported&nbsp;versions
210 <tr><td><tt>anope</tt>
211 <td><a href="http://www.anope.org/">Anope Services</a>
212 <font size=-1>[<tt>www.anope.org</tt>]</font>
213 <td>All versions
214 <tr><td><tt>auspice</tt>
215 <td>Auspice Services
216 <td>2.5 and later
217 <tr><td><tt>bolivia</tt>
218 <td>Bolivia IRC Services
219 <td>1.2.0
220 <tr><td><tt>cygnus</tt>
221 <td><a href="http://www.habber.net/services/index.php">Cygnus</a>
222 <font size=-1>[<tt>www.habber.net</tt>]</font>
223 <td>0.2.0
224 <tr><td><tt>daylight</tt>
225 <td>Daylight
226 <td>12
227 <tr><td><tt>epona</tt>
228 <td>Epona IRC Services
229 <td>1.3.0 and later
230 <tr><td><tt>hybserv</tt>
231 <td><a href="http://www.hybserv.net/">HybServ</a>
232 <font size=-1>[<tt>www.hybserv.net</tt>]</font>
233 <td>All 1.x versions
234 <tr><td><tt>ircs-1.2</tt>
235 <td>Internet Relay Chat Services (IRCS)
236 <td>1.2, 1.3
237 <tr><td><tt>magick-1.4</tt>
238 <td>Magick IRC Services (Magick I)
239 <td>1.4
240 <tr><td><tt>ptlink</tt>
241 <td><a href="http://sourceforge.net/projects/ptlinksoft/">PTlink
242 Services</a> <font size=-1>[<tt>sourceforge.net</tt>]</font>
243 <td>2.13.0 through 2.26-eol.1
244 <tr><td><tt>sirv</tt>
245 <td><a href="http://www.sirv.net/">SirvNET Services</a>
246 <font size=-1>[<tt>www.sirv.net</tt>]</font>
247 <td>2.9.0 and earlier
248 <tr><td><tt>trircd-4.26</tt>
249 <td>trircd IRC Services
250 <td>4.26
251 <tr><td><tt>wrecked-1.2</tt>
252 <td>WreckedNet IRC Services
253 <td>1.2.0
254 </table>
255 </div>
256
257 <p>Note that the following programs and versions are <i>not</i> supported,
258 because they do not store data in standard disk files:
259 <ul>
260 <li>Anope 1.7.11 and later, when using MySQL databases (a standard file
261 format is still available as of version 1.7.19)
262 <li>PTlink Services 3.0.0 and later
263 </ul>
264
265 <p>Additional options are available for the following data file types:
266
267 <p><b><tt>anope</tt></b>
268 <ul>
269 <li><tt>-ircd=<i>protocol</i></tt>: Selects the protocol to use for
270 interpreting channel modes. By default, only basic channel modes
271 (<tt>+i</tt>, <tt>+k</tt>, <tt>+l</tt>, <tt>+m</tt>, <tt>+n</tt>,
272 <tt>+p</tt>, <tt>+s</tt>, and <tt>+t</tt>) will be imported for
273 channel mode locks; to import extended modes provided by particular
274 specify the corresponding protocol from the following list (for
275 Anope 1.7.6 and later, use the same name as in the
276 <tt>IRCDModule</tt> configuration directive):
277 <ul>
278 <li><tt>bahamut</tt> for Bahamut
279 <li><tt>dreamforge</tt> for Dreamforge
280 <li><tt>hybrid</tt> for IRCD-Hybrid
281 <li><tt>ptlink</tt> for PTlink IRCd
282 <li><tt>ultimate2</tt> for UltimateIRCD 2.x
283 <li><tt>ultimate3</tt> for UltimateIRCD 3.x
284 <li><tt>unreal</tt> for UnrealIRCd
285 <li><tt>viagra</tt> for Viagra IRCd
286 </ul>
287 <li><tt>-encryption=<i>type</i></tt>: Selects the encryption type for
288 databases from Anope 1.7.18 and later. These versions of Anope do
289 not record the encryption type used with passwords stored in the
290 databases; in order to use such passwords, you must specify the
291 proper encryption type with this option:
292 <ul>
293 <li><tt>none</tt>: No encryption (<tt>enc_none</tt> module)
294 <li><tt>md5</tt>: MD5 encryption (<tt>enc_md5</tt>,
295 <tt>enc_old</tt> modules)
296 <li><tt>sha1</tt>: SHA-1 encryption (<tt>enc_sha1</tt>
297 module)&mdash;<i>not supported</i> by Services
298 (passwords will be converted correctly, but will
299 not be usable without a third-party module)
300 </ul>
301 <b>Note:</b> If you use this option and your database contains a
302 mix of encrypted and unencrypted passwords from Anope 1.7.17 or
303 earlier, some of the passwords will not work.
304 </ul>
305
306 <p><b><tt>cygnus</tt></b>
307 <ul>
308 <li><tt>-tzfile=<i>filename</i></tt>: Specifies an alternative time zone
309 file to use when loading nickname time zone data. <tt>convert-db</tt>
310 defaults to the data from the <tt>cygnus.zone</tt> file distributed
311 with Cygnus 0.2.0; if you have modified this file or created your
312 own time zone list, you will need to use this option to get nickname
313 time zones converted correctly.
314 <li><tt>-no-timezones</tt>: Causes all nickname time zone settings to be
315 reset to default (the time zone Services runs in).
316 <li><tt>-reset-memo-limits</tt>: Causes all nickname memo limits to be reset
317 to default; see the notes on Cygnus database conversion.
318 </ul>
319
320 <p><b><tt>hybserv</tt></b>
321 <ul>
322 <li><tt>-crypt</tt>: Indicates that all passwords are encrypted. Without
323 this option, all passwords are assumed to be in plain text.
324 </ul>
325
326 <p align=right><font size="-1"><a href="#top">Back to top</a></font>
327
328 <a name=3-2></a>
329 <h4>5-3-2. Notes on converting databases from particular programs</h4>
330
331 <p>Note that this is not a comprehensive list of differences; only the
332 major differences and types of data that cannot be converted are listed.
333
334 <p><b>All programs</b>
335 <ul>
336 <li>The setter and reason for a forbidden nickname or channel will not be
337 imported.
338 <li>Channel privilege level settings (the equivalent of the ChanServ
339 <tt>LEVELS</tt> command), on programs that support them, will not
340 be imported; all channels' privilege levels will be reset to the
341 default values.
342 <li>Services does not record the setter and last used time for channel
343 access entries; this data will be lost on conversion for programs
344 that do record it.
345 <li>Services does not support "bots" or a "BotServ", and all such data will
346 be lost on conversion.
347 </ul>
348
349 <p><b>Anope</b>
350 <ul>
351 <li>For version 1.7.11 and later, databases must be stored using the
352 standard ("FFF") format; MySQL databases are not supported.
353 <li>Anope versions through 1.7.17 contain the MD5 encryption bug present
354 in versions of IRC Services before 4.5; as a result, encrypted
355 passwords will not work by default. As a workaround, you can
356 enable the
357 <a href="a.html#encryption/md5.EnableAnopeWorkaround"><tt>EnableAnopeWorkaround</tt></a>
358 configuration option for the <tt>encryption/md5</tt> module in
359 <tt>modules.conf</tt>, but be aware that this may reduce the
360 security of your passwords. There are also rare cases in which
361 passwords may be truncated in the databases; if you encounter such
362 a case, the password will have to be changed manually by a Services
363 administrator.</li>
364 <li>Services does not store the following information; it will be lost when
365 the databases are converted:
366 <ul>
367 <li>ICQ number for nicknames
368 <li>Last used time for channel access entries
369 </ul>
370 <li>The NickServ <tt>SET AUTOOP OFF</tt> option present in Anope 1.7.15 and
371 later is converted to <tt>SET NOOP ON</tt>; however, the behavior
372 in of <tt>NOOP</tt> in Services is slightly different, as it only
373 prevents the nickname from being added to channel access lists (the
374 nickname will still be auto-opped if it already has that privilege
375 in a channel).
376 <li>Services does not allow multiple users to have Services super-user
377 privileges (except temporarily with the
378 <a href="4.html#oper.su"><tt>SU</tt></a> command); all users with
379 "root" privileges in Anope will be converted to Services
380 administrators.
381 <li>Services does not distinguish between using the ChanServ <tt>OP</tt>,
382 <tt>VOICE</tt>, and related commands on oneself or on other users;
383 both operations use the same privilege level.
384 <li>Services does not support the ChanServ <tt>SECUREFOUNDER</tt>,
385 <tt>SIGNKICK</tt>, or <tt>XOP</tt> settings. (<tt>XOP</tt>-style
386 commands can be enabled for all channels by loading the
387 <tt>chanserv/access-xop</tt> module.)
388 <li>Nickname requests (nicknames which have been registered but not
389 confirmed via E-mail) are discarded; users with pending nickname
390 requests will need to re-register.
391 </ul>
392
393 <p><b>Auspice</b>
394 <ul>
395 <li>The NickServ <tt>NOOP</tt> option behaves slightly differently in
396 Services: it prevents the nickname from being added to channel
397 access lists, but the nickname will still be auto-opped if it
398 already has that privilege in a channel.
399 <li>The ChanServ <tt>TIMEOP</tt> feature in version 2.6 and later is not
400 supported. Nicknames on a channel's <tt>TIMEOP</tt> list will not
401 be added to the channel's access list for Services, and thus will
402 have no privileges on the channel.
403 <li>Services does not support "root" and "master" privilege levels as in
404 Auspice. There can only be one root nickname, which is set in
405 <tt>modules.conf</tt>; all root/master settings in the data files
406 will be discarded. (Admin/oper settings will be retained.) Note
407 that Services admins can perform any function (except modifying the
408 admin list), including modifying Services settings and shutting
409 down Services.
410 <li>NickServ <tt>AUTH</tt>, <tt>COMMENT</tt>, <tt>NOTE</tt>, <tt>LOCK</tt>,
411 <tt>MARK</tt>, <tt>SET KILL HIGH</tt>, <tt>SETFLAG AUTOJOIN</tt>,
412 and <tt>SETMLOCK</tt>, as well as ChanServ <tt>BADWORDS</tt>,
413 <tt>FREEZE</tt>, and <tt>MARK</tt>, are not supported. Nickname
414 notes will be converted to non-expiring memos with the user
415 themselves as the sender; other data will be lost.
416 <li>Services uses a different news system than Auspice; network and channel
417 news items will not be converted.
418 <li>Aside from the above, Services does not store the following
419 information; it will be lost when the databases are converted:
420 <ul>
421 <li>UIN, age, and gender for nicknames
422 <li>Last <tt>GETPASS</tt> user and <tt>HOLD</tt> setter and reason
423 for channels
424 </ul>
425 <li>E-mailing of log files is not supported.
426 </ul>
427
428 <p><b>Bolivia</b>
429 <ul>
430 <li>The NickServ <tt>NOOP</tt> option behaves slightly differently in
431 Services: it prevents the nickname from being added to channel
432 access lists, but the nickname will still be auto-opped if it
433 already has that privilege in a channel.
434 <li>Limiting channels to privileged users (the <tt>LEVEL</tt> command) is
435 not supported, and such restrictions will be discarded when
436 converting the databases. However, some IRC servers (such as
437 Unreal) have channel modes allowing channels to be limited to IRC
438 operators or administrators only, and Services allows those modes
439 to be locked on with the <tt>SET MLOCK</tt> command.
440 <li>ChanServ <tt>FREEZE</tt> is not supported.
441 <li>ChanServ <tt>HOLD</tt> setter will be lost when converting.
442 <li>E-mailing of log files is not supported.
443 </ul>
444
445 <p><b>Cygnus</b>
446 <ul>
447 <li>Services does not store the UIN, real name, age, sex, or location for
448 nicknames; this information will be lost when the databases are
449 converted.
450 <li>Services does not send replies using <tt>PRIVMSG</tt>; the
451 <tt>NOTICE</tt> and <tt>PRIVMSG</tt> nickname settings will be
452 ignored.
453 <li>The following options/features are not supported:
454 <ul>
455 <li>NickServ <tt>NEVEROP</tt> and <tt>NOSUCCESSOR</tt>
456 <li>ChanServ <tt>LIMITED</tt>
457 <li>MemoServ <tt>RECEIPTS</tt>
458 <li>RootServ <tt>MARK</tt>
459 </ul>
460 <li>Nicknames designated as CSOPs will be converted to Services operators.
461 Note that the privileges granted by IRC Services to Services
462 operators are different from those granted by Cygnus to CSOPs.
463 <li>Nicknames will retain their memo limit settings in the converted data;
464 however, they will not be affected by changes to the
465 <a href="a.html#memoserv/main.MSMaxMemos"><tt>MSMaxMemos</tt></a>
466 setting. (Memo limits can be reset to the default, which follows
467 the <tt>MSMaxMemos</tt> setting, with the <tt>-reset-memo-limits</tt>
468 option.)
469 <li>If you have modified the time zone list used by Cygnus
470 (<tt>cygnus.zone</tt>), nickname time zones will not be transferred
471 correctly by default. Use the <tt>-tzfile=</tt> option to ensure
472 that time zones are loaded from your time zone file, or use the
473 <tt>-no-timezones</tt> option to reset all time zone settings to
474 default.
475 <li>Authentication for channels is not supported; authentication codes and
476 "verify" information will be discarded.
477 <li>Channel access list entries in IRC Services must always be registered
478 nicknames; <tt><i>user</i>@<i>host</i></tt> entries, and any
479 entries not matching a registered nickname, will be deleted.
480 <li>While the channel topic-lock setting will be retained, the lock level
481 (founder/SOP/AOP/HOP/VOP) will be reset to the IRC Services default
482 (AOP). If you use the <tt>LEVELS</tt> command (in the
483 <tt>chanserv/access-levels</tt> submodule), you can change the
484 level of the <tt>TOPIC</tt> command to set which users are
485 allowed to change the topic.
486 <li>While not directly related to the databases, note that Services uses
487 the <a href="4.html#nick.auth"><tt>AUTH</tt></a> command, not the
488 <tt>REGISTER</tt> or <tt>SET EMAIL</tt> commands, to authenticate
489 nicknames.
490 </ul>
491
492 <p><b>Daylight</b>
493 <ul>
494 <li>Services does not support the <tt>XMANAGEMENT</tt> channel setting.
495 </ul>
496
497 <p><b>Epona</b>
498 <ul>
499 <li>Epona contains the MD5 encryption bug present in versions of IRC
500 Services before 4.5; as a result, encrypted passwords will not work
501 by default. As a workaround, you can enable the
502 <a href="a.html#encryption/md5.EnableAnopeWorkaround"><tt>EnableAnopeWorkaround</tt></a>
503 configuration option for the <tt>encryption/md5</tt> module in
504 <tt>modules.conf</tt>, but be aware that this may reduce the
505 security of your passwords. There are also rare cases in which
506 passwords may be truncated in the databases; if you encounter such
507 a case, the password will have to be changed manually by a Services
508 administrator.</li>
509 <li>Services does not store the following information; it will be lost when
510 the databases are converted:
511 <ul>
512 <li>ICQ number for nicknames
513 <li>Last used time for channel access entries
514 </ul>
515 <li>Services does not distinguish between using the ChanServ <tt>OP</tt>,
516 <tt>VOICE</tt>, and related commands on oneself or on other users.
517 <li>By default, only basic channel modes (<tt>+i</tt>, <tt>+k</tt>,
518 <tt>+l</tt>, <tt>+m</tt>, <tt>+n</tt>, <tt>+p</tt>, <tt>+s</tt>,
519 and <tt>+t</tt>) will be imported for channel mode locks. To
520 import extended modes provided by particular IRC servers, use one
521 of the following command-line options:
522 <ul>
523 <li><tt>-ircd=bahamut</tt> for Bahamut
524 <li><tt>-ircd=ultimate2</tt> for UltimateIRCD
525 <li><tt>-ircd=unreal</tt> for UnrealIRCd
526 </ul>
527 </ul>
528
529 <p><b>HybServ</b>
530 <ul>
531 <li>Services does not store GSM, phone, or ICQ number for nicknames; this
532 information will be lost when the databases are converted.
533 <li>Services does not have the concept of "permanent passwords", as in
534 HybServ 1.6.1+UniBG, and such passwords will be discarded on
535 import.
536 <li>Services does not support the NickServ <tt>AUTOMASK</tt>, <tt>HIDE
537 URL</tt>, <tt>NOREGISTER</tt>, or <tt>NOCHANOPS</tt> settings, or
538 the ChanServ <tt>GUARD</tt> or <tt>VERBOSE</tt> settings.
539 <li>The NickServ <tt>NOOP</tt> option behaves slightly differently in
540 Services: it prevents the nickname from being added to channel
541 access lists, but the nickname will still be auto-opped if it
542 already has that privilege in a channel.
543 <li>The NickServ <tt>HIDE ALL</tt> setting is treated as a combination of
544 <tt>HIDE EMAIL</tt>, <tt>HIDE USERMASK</tt>, and <tt>HIDE QUIT</tt>.
545 The nickname URL and options cannot be hidden.
546 <li>Temporary forbids are imported as permanent (Services does not support
547 the notion of a "temporary" or "timed" forbid).
548 <li>"Forgotten" channels are not supported, and will not be imported.
549 <li>Services does not have a system of "operator modes" like HybServ, and
550 no operator mode information will be imported.
551 <li>Statistics information (maximum number of users/channels/etc.) will not
552 be imported.
553 <li>The founder of a channel will be removed from the channel's access list
554 (founders always have full channel privileges and do not need to be
555 added to the access list).
556 <li>Channel privilege levels will be reset to the Services defaults on
557 import. Channel access levels will also be modified to fit within
558 the -999&nbsp;.&nbsp;.&nbsp;.&nbsp;999 range used by Services, as follows:
559 <p align=center><table border=1>
560 <tr><th>HybServ level<th>Services level
561 <tr><td align=center>-10000<td align=center>-999
562 <tr><td align=center>-9999&nbsp;.&nbsp;.&nbsp;.&nbsp;-10<td align=center>-999&nbsp;.&nbsp;.&nbsp;.&nbsp;-1
563 <tr><td align=center>-9&nbsp;.&nbsp;.&nbsp;.&nbsp;-1<td align=center>-1
564 <tr><td align=center>0&nbsp;.&nbsp;.&nbsp;.&nbsp;5<td align=center>0&nbsp;.&nbsp;.&nbsp;.&nbsp;30
565 <tr><td align=center>5&nbsp;.&nbsp;.&nbsp;.&nbsp;10<td align=center>30&nbsp;.&nbsp;.&nbsp;.&nbsp;50
566 <tr><td align=center>10&nbsp;.&nbsp;.&nbsp;.&nbsp;15<td align=center>50&nbsp;.&nbsp;.&nbsp;.&nbsp;100
567 <tr><td align=center>15&nbsp;.&nbsp;.&nbsp;.&nbsp;20<td align=center>100&nbsp;.&nbsp;.&nbsp;.&nbsp;110
568 <tr><td align=center>20&nbsp;.&nbsp;.&nbsp;.&nbsp;200<td align=center>110&nbsp;.&nbsp;.&nbsp;.&nbsp;200
569 <tr><td align=center>200&nbsp;.&nbsp;.&nbsp;.&nbsp;1000<td align=center>200&nbsp;.&nbsp;.&nbsp;.&nbsp;300
570 <tr><td align=center>1000&nbsp;.&nbsp;.&nbsp;.&nbsp;9000<td align=center>300&nbsp;.&nbsp;.&nbsp;.&nbsp;900
571 <tr><td align=center>9000&nbsp;.&nbsp;.&nbsp;.&nbsp;9999<td align=center>900&nbsp;.&nbsp;.&nbsp;.&nbsp;999
572 <tr><td align=center>10000<td align=center>999
573 </table>
574 <p><b>WARNING:</b> As a result of differences in the default level settings
575 between HybServ and Services, some users will have access to commands which
576 they did not previously have access to. In particular, the <tt>ACCESS</tt>
577 command is available to all users with access level 40 (HybServ level 8) or
578 above, and the <tt>CLEAR</tt> command is available to all users with
579 access level 100 (HybServ level 15) or above. Conversely, the
580 <tt>INVITE</tt> command is available only to users with access level 50
581 (HybServ level 10) or above; auto-voice users cannot use it.
582 </ul>
583
584 <p><b>IRCS</b>
585 <ul>
586 <li>By default, IRCS supports channels with names longer than 63 characters
587 (including the leading "#"). Services does not support these by
588 default, and such channels will not be imported.
589 <li>Channel autoop/autovoice cannot be set for individual nicknames. All
590 nicks with appropriate access will be opped even if ChanServ
591 <tt>SET AUTOOP OFF</tt> was used for the nick.
592 <li>The numeric access level for <tt>SOP</tt> is different from that used
593 in Services, so some access levels will be altered to match the
594 default <tt>SOP</tt> level in Services. (Channel privileges will
595 remain unchanged.)
596 <li>The "senior", "junior", and "helper" OperServ access levels do not
597 exist in Services. Users on the "senior" list will be moved to the
598 Services admin list; users on other lists will be moved to the
599 Services operator list. <b>WARNING:</b> As a result of the above,
600 users on the "senior" list will be given access to the
601 <tt>JUPE</tt> and <tt>LISTIGNORE</tt> commands.
602 </ul>
603
604 <p><b>Magick I 1.4</b>
605 <ul>
606 <li>Services does not send replies using <tt>PRIVMSG</tt>; the
607 <tt>NI_PRIVMSG</tt> nickname setting will be ignored.
608 <li>Services does not have a "channel news" system like Magick, and all
609 channel news items will be discarded.
610 </ul>
611
612 <p><b>PTlink</b>
613 <ul>
614 <li>PTlink supports several encryption methods; of these, the "JP2" method
615 is not supported by Services, and any passwords encrypted with this
616 method will be reset to the respective nick or channel name.
617 <li>Services does not store the following information; it will be lost when
618 the databases are converted:
619 <ul>
620 <li>ICQ number, location, birthdate, time of last identify, and
621 authentication code (2.22.0 and later) for nicknames
622 <li>maximum number of users and time of maximum for channels
623 </ul>
624 <li>An apparent bug in PTlink causes the successor field of some channels
625 to be corrupted; this will result in warnings when loading the
626 channel database.
627 <li>What PTlink refers to as "SXlines" are known as "SGlines" in Services;
628 SXline database records (in versions of PTlink that support it)
629 will be converted to SGline records.
630 </ul>
631
632 <p><b>SirvNET</b>
633 <ul>
634 <li>The NickServ <tt>NOOP</tt> option behaves slightly differently in
635 Services: it prevents the nickname from being added to channel
636 access lists, but the nickname will still be auto-opped if it
637 already has that privilege in a channel.
638 <li>Limiting channels to priviliged users (the <tt>LEVEL</tt> command) is
639 not supported, and such restrictions will be discarded when
640 converting the databases. However, some IRC servers (such as
641 Unreal) have channel modes allowing channels to be limited to IRC
642 operators or administrators only, and Services allows those modes
643 to be locked on with the <tt>SET MLOCK</tt> command.
644 <li>NickServ <tt>AUTH</tt> and ChanServ <tt>FREEZE</tt> are not supported.
645 <li>ChanServ <tt>HOLD</tt> setter and reason will be lost when converting.
646 <li>E-mailing of log files is not supported.
647 </ul>
648
649 <p><b>trircd</b>
650 <ul>
651 <li><tt>SET EXCEPTION</tt>, <tt>SET INVITES</tt>, <tt>HIDE OPTIONS</tt>,
652 and <tt>HIDE DESC</tt> channel settings are not supported.
653 </ul>
654
655 <p><b>Wrecked 1.2.0</b>
656 <ul>
657 <li>Services does not send replies using <tt>PRIVMSG</tt>; the
658 <tt>NI_PRIVMSG</tt> nickname setting will be ignored.
659 <li>The <tt>VOPALL</tt> channel setting is not supported.
660 </ul>
661
662 <p align=right><font size="-1"><a href="#top">Back to top</a></font>
663
664 <p><hr>
665
666 <p align=right><font size=-1><a href=4.html>Previous section: Services command reference</a> |
667 <a href=index.html>Table of Contents</a></font>
668
669 </body>
670 </html>