]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000180.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 000180.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] Services 5.0 Miunor Bugs/glitches/suggestions
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.0%20Miunor%20Bugs/glitches/suggestions&In-Reply-To=3c5d4cdc.47342%40achurch.org">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="000179.html">
11 <LINK REL="Next" HREF="000181.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] Services 5.0 Miunor Bugs/glitches/suggestions</H1>
15 <B>Mark Hetherington</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205.0%20Miunor%20Bugs/glitches/suggestions&In-Reply-To=3c5d4cdc.47342%40achurch.org"
17 TITLE="[IRCServices Coding] Services 5.0 Miunor Bugs/glitches/suggestions">mark at mhetherington.demon.co.uk
18 </A><BR>
19 <I>Sun Feb 3 13:07:30 PST 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000179.html">[IRCServices Coding] Services 5.0 alpha 18 released
22 </A></li>
23 <LI>Next message: <A HREF="000181.html">[IRCServices Coding] Services 5.0 Bug in oper.db
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#180">[ date ]</a>
27 <a href="thread.html#180">[ thread ]</a>
28 <a href="subject.html#180">[ subject ]</a>
29 <a href="author.html#180">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Version 5 is definitely coming together very well now.
35
36 Been running the latest version on a production network and the following
37 issues came up. All reported on a Network of Unreal servers running Services
38 5.0a18.
39
40 1) Bug: When the ChanServ and Nickserv LIST command is restricted to opers
41 only, it still displays in the list of standard commands available to all
42 users. It ought to be removed from the commands list when not available to a
43 user.
44
45 2) Suggestion: A configuration file directive to remove/disable GetPass
46 would be a welcome addition. The introduction of SendPass into the main
47 distribution removes the main need for GetPass (password recovery) so the
48 abiity to easily remove GetPass commands from the modules and references in
49 helpfiles would be useful.
50
51 3) Bug: Memoserv send does not always confirm that a memo has been sent even
52 though it has. This only seems to affect some users and I have yet to find
53 what it is about particular users that causes this.
54
55 4) Bug: Help responses which involve 2 pseudo client names do not appear to
56 display correctly. E.g. the /cs help register command will display the name
57 of the ChanServ client correctly, but seemingly a random string for the
58 NickServ client
59
60 -ChanServ- Syntax: SENDPASS channel
61 -ChanServ-
62 -ChanServ- Sends you an E-mail message containing the password for the
63 -ChanServ- given channel. You must be the founder of the channel to
64 -ChanServ- use this command, and you must first identify for your
65 -ChanServ- nickname with the xxx.xxx.xxx.xxx.xxx IDENTIFY command.
66
67 (the xxx refers to a user's hostname masked for privacy which managed to
68 become the client name for NickServ during one services run. This same host
69 name was displayed in that place to all users on the network. Previous runs
70 had other strings which were sometimes &quot;random&quot; garbage.
71
72 5) Bug: The Network statistics link in the httpd module does not operate at
73 all. On our network we run an existing StatServ client, so the services one
74 is named StatServ2. I could not see anything in the code/setup that would
75 cause this to affect the httpd module but thought I should mention it in
76 case.
77
78 6) Another &quot;unhandled&quot; message for the list, services reports but is unable
79 to process /who 0 o commands (users trying to list online opers) generating:
80
81 unknown message from server (:nick 4 [Did a /who 0 o])
82
83 7) Suggestion: every hyperlink clicked in the httpd pages results in the
84 following log entry:
85
86 httpd/main: Accepted connection from xxx.xxx.xxx.xxx:nnnn
87
88 This suggestion is twofold, firstly a more defined log entry specifying the
89 access made and secondly, logging the httpd client messages to a seperate
90 log file. It might actually be useful to log each client to it's own log
91 file, with the central file reserved for messages related to overall
92 operation.
93
94 8) Rehash produces an odd error message:
95
96 Received SIGHUP, rehashing.
97 sockets: select(): Interrupted system call
98
99 Not sure how important this is but if it is important enough to log, it is
100 probably something that shouldn't be happening :)
101
102 9) Not sure if this is a known problem listed anywhere but I haven't found
103 it in the docs, Services 5 will not parse a Version 4.5.x exception.db file.
104 The following error appears in the log file:
105
106 database/version4: Read error on exception.db
107
108
109 I think that covers everything in today's findings that I haven't found in
110 known bugs or other comments :)
111
112 Mark.
113
114
115 </PRE>
116
117 <!--endarticle-->
118 <HR>
119 <P><UL>
120 <!--threads-->
121 <LI>Previous message: <A HREF="000179.html">[IRCServices Coding] Services 5.0 alpha 18 released
122 </A></li>
123 <LI>Next message: <A HREF="000181.html">[IRCServices Coding] Services 5.0 Bug in oper.db
124 </A></li>
125 <LI> <B>Messages sorted by:</B>
126 <a href="date.html#180">[ date ]</a>
127 <a href="thread.html#180">[ thread ]</a>
128 <a href="subject.html#180">[ subject ]</a>
129 <a href="author.html#180">[ author ]</a>
130 </LI>
131 </UL>
132
133 </body></html>