]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] Services 5.0a21 problems | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205.0a21%20problems&In-Reply-To="> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="000292.html"> | |
11 | <LINK REL="Next" HREF="000302.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] Services 5.0a21 problems</H1> | |
15 | <B>Mark Hetherington</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205.0a21%20problems&In-Reply-To=" | |
17 | TITLE="[IRCServices Coding] Services 5.0a21 problems">mark at ctcp.net | |
18 | </A><BR> | |
19 | <I>Sat Feb 16 09:32:03 PST 2002</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="000292.html">[IRCServices Coding] More bugs and suggestions for Version 5.0 | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="000302.html">[IRCServices Coding] SegFault | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#301">[ date ]</a> | |
27 | <a href="thread.html#301">[ thread ]</a> | |
28 | <a href="subject.html#301">[ subject ]</a> | |
29 | <a href="author.html#301">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Services appears to be losing the operserv oper/admin list. When it starts | |
35 | up it seems to ignore or throw away the current contents of the database | |
36 | and the entries have to be added back in. | |
37 | ||
38 | The only error in the log is: | |
39 | [Feb 16 17:11:19 2002] IRC Services 5.0a21 starting up | |
40 | [Feb 16 17:11:19 2002] database/version4: Read error on nick.db | |
41 | [Feb 16 17:24:14.156110 2002] debug: Loading module `nickserv/main' | |
42 | [Feb 16 17:24:14.170455 2002] database/version4: Read error on nick.db | |
43 | [Feb 16 17:24:14.170563 2002] debug: Successfully loaded module | |
44 | `nickserv/main' | |
45 | ||
46 | Not sure why there is a read error, but NickServ seems to operate | |
47 | successfully regardless of it. I guess it may have some bearing on the | |
48 | operserv list bug. | |
49 | ||
50 | As a suggestion, could the database error reporting be made provide a | |
51 | little more information as to which failure occurred. E.g. read error on %s | |
52 | by currentfunction. | |
53 | ||
54 | ||
55 | ||
56 | -- | |
57 | Mark. | |
58 | ||
59 | ||
60 | ||
61 | </PRE> | |
62 | ||
63 | <!--endarticle--> | |
64 | <HR> | |
65 | <P><UL> | |
66 | <!--threads--> | |
67 | <LI>Previous message: <A HREF="000292.html">[IRCServices Coding] More bugs and suggestions for Version 5.0 | |
68 | </A></li> | |
69 | <LI>Next message: <A HREF="000302.html">[IRCServices Coding] SegFault | |
70 | </A></li> | |
71 | <LI> <B>Messages sorted by:</B> | |
72 | <a href="date.html#301">[ date ]</a> | |
73 | <a href="thread.html#301">[ thread ]</a> | |
74 | <a href="subject.html#301">[ subject ]</a> | |
75 | <a href="author.html#301">[ author ]</a> | |
76 | </LI> | |
77 | </UL> | |
78 | ||
79 | </body></html> |