1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding] Services
5.0 Miunor Bugs/glitches/suggestions
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=">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"000182.html">
11 <LINK REL=
"Next" HREF=
"000185.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding] Services
5.0 Miunor Bugs/glitches/suggestions
</H1>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205.0%20Miunor%20Bugs/glitches/suggestions&In-Reply-To="
17 TITLE=
"[IRCServices Coding] Services 5.0 Miunor Bugs/glitches/suggestions">achurch at achurch.org
19 <I>Mon Feb
4 07:
51:
13 PST
2002</I>
21 <LI>Previous message:
<A HREF=
"000182.html">[IRCServices Coding] Services
5.0 Bug in oper.db
23 <LI>Next message:
<A HREF=
"000185.html">[IRCServices Coding] Services
5.0 Miunor Bugs/glitches/suggestions
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#183">[ date ]
</a>
27 <a href=
"thread.html#183">[ thread ]
</a>
28 <a href=
"subject.html#183">[ subject ]
</a>
29 <a href=
"author.html#183">[ author ]
</a>
34 <PRE>><i>1) Bug: When the ChanServ and Nickserv LIST command is restricted to opers
35 </I>><i>only, it still displays in the list of standard commands available to all
36 </I>><i>users. It ought to be removed from the commands list when not available to a
39 I don't consider this a bug (in fact, I think I had it that way at one
40 point and reversed it), but it seems reasonable enough. Done.
42 ><i>2) Suggestion: A configuration file directive to remove/disable GetPass
43 </I>><i>would be a welcome addition. The introduction of SendPass into the main
44 </I>><i>distribution removes the main need for GetPass (password recovery) so the
45 </I>><i>abiity to easily remove GetPass commands from the modules and references in
46 </I>><i>helpfiles would be useful.
50 ><i>3) Bug: Memoserv send does not always confirm that a memo has been sent even
51 </I>><i>though it has. This only seems to affect some users and I have yet to find
52 </I>><i>what it is about particular users that causes this.
54 I haven't been able to reproduce this, and can't fix it without more
57 ><i>4) Bug: Help responses which involve
2 pseudo client names do not appear to
58 </I>><i>display correctly. E.g. the /cs help register command will display the name
59 </I>><i>of the ChanServ client correctly, but seemingly a random string for the
60 </I>><i>NickServ client
62 I can't reproduce this.
64 ><i>5) Bug: The Network statistics link in the httpd module does not operate at
67 This is known (see the FIXME in httpd/dbaccess.c).
69 ><i>6) Another
"unhandled
" message for the list, services reports but is unable
70 </I>><i>to process /who
0 o commands (users trying to list online opers) generating:
72 </I>><i>unknown message from server (:nick
4 [Did a /who
0 o])
74 This is a HELP message (the /who is processed by the client's server).
75 I'll add it to the ignore list.
77 ><i>7) Suggestion: every hyperlink clicked in the httpd pages results in the
78 </I>><i>following log entry:
80 </I>><i>httpd/main: Accepted connection from xxx.xxx.xxx.xxx:nnnn
82 </I>><i>This suggestion is twofold, firstly a more defined log entry specifying the
83 </I>><i>access made and secondly, logging the httpd client messages to a seperate
84 </I>><i>log file. It might actually be useful to log each client to it's own log
85 </I>><i>file, with the central file reserved for messages related to overall
88 I don't like the proliferation of log files that would create; if it
89 bothers you to have everything in one logfile, just write a script that
90 parses them out to separate files or something. As for the other point, an
91 access-log-like thing is under consideration.
93 ><i>8) Rehash produces an odd error message:
95 </I>><i>Received SIGHUP, rehashing.
96 </I>><i>sockets: select(): Interrupted system call
98 This is because the signal interrupts select() which is waiting for
99 input from the remote server, and probably shouldn't be logged as it's
100 normal behavior. Fixed.
102 ><i>9) Not sure if this is a known problem listed anywhere but I haven't found
103 </I>><i>it in the docs, Services
5 will not parse a Version
4.5.x exception.db file.
104 </I>><i>The following error appears in the log file:
106 </I>><i>database/version4: Read error on exception.db
108 Can you send me an example database that has this problem?
111 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>
112 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
120 <LI>Previous message:
<A HREF=
"000182.html">[IRCServices Coding] Services
5.0 Bug in oper.db
122 <LI>Next message:
<A HREF=
"000185.html">[IRCServices Coding] Services
5.0 Miunor Bugs/glitches/suggestions
124 <LI> <B>Messages sorted by:
</B>
125 <a href=
"date.html#183">[ date ]
</a>
126 <a href=
"thread.html#183">[ thread ]
</a>
127 <a href=
"subject.html#183">[ subject ]
</a>
128 <a href=
"author.html#183">[ author ]
</a>