software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000185.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=3c5dce27.54332%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="000183.html">
  11    <LINK REL="Next"  HREF="000184.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=3c5dce27.54332%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 16:41:22 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000183.html">[IRCServices Coding] Services 5.0 Miunor Bugs/glitches/suggestions
  22 </A></li>
  23         <LI>Next message: <A HREF="000184.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#185">[ date ]</a>
  27               <a href="thread.html#185">[ thread ]</a>
  28               <a href="subject.html#185">[ subject ]</a>
  29               <a href="author.html#185">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Thanks for the prompt response and fixes.
  35
  36 &gt;<i> &gt;3) Bug: Memoserv send does not always confirm that a memo has
  37 </I>&gt;<i> been sent even
  38 </I>&gt;<i> &gt;though it has. This only seems to affect some users and I have
  39 </I>&gt;<i> yet to find
  40 </I>&gt;<i> &gt;what it is about particular users that causes this.
  41 </I>&gt;<i>
  42 </I>&gt;<i>      I haven't been able to reproduce this, and can't fix it without more
  43 </I>&gt;<i> information.
  44 </I>
  45 Trying to track this down. Any ideas as to what could cause such an issue? I
  46 get it all the time. I am services root but even when using a different non
  47 linked nickname I can still get it (using same client and setup that worked
  48 with 4.5.x). Other users that have experienced it have no &quot;status&quot; so I do
  49 not think my services access is affecting it in any case. I will get chance
  50 to try on a completely different system and connection tomorrow (work) and
  51 go from there.
  52
  53 &gt;<i> &gt;4) Bug: Help responses which involve 2 pseudo client names do
  54 </I>&gt;<i> not appear to
  55 </I>&gt;<i> &gt;display correctly. E.g. the /cs help register command will
  56 </I>&gt;<i> display the name
  57 </I>&gt;<i> &gt;of the ChanServ client correctly, but seemingly a random string for the
  58 </I>&gt;<i> &gt;NickServ client
  59 </I>&gt;<i>
  60 </I>&gt;<i>      I can't reproduce this.
  61 </I>
  62 Off-list email sent of config and details of a network exhibiting said
  63 problem in case it is a combination of settings which cause this.
  64
  65 &gt;<i>      I don't like the proliferation of log files that would create; if it
  66 </I>&gt;<i> bothers you to have everything in one logfile, just write a script that
  67 </I>&gt;<i> parses them out to separate files or something.  As for the other
  68 </I>&gt;<i> point, an
  69 </I>&gt;<i> access-log-like thing is under consideration.
  70 </I>
  71 It doesn't bother me having everything in one log file. It was mainly the
  72 lack of information in the httpd messages and their high proliferation rate
  73 compared with other modules which made me consider a seperate log file for
  74 it. Multiple log files was just an extension of the idea for discussion. The
  75 access log would solve the information in the message, but hopefully this
  76 would be coupled with a simple (configuration possibly) way to disable the
  77 standard message in the main log file.
  78
  79 &gt;<i> &gt;9) Not sure if this is a known problem listed anywhere but I
  80 </I>&gt;<i> haven't found
  81 </I>&gt;<i> &gt;it in the docs, Services 5 will not parse a Version 4.5.x
  82 </I>&gt;<i> exception.db file.
  83 </I>&gt;<i> &gt;The following error appears in the log file:
  84 </I>&gt;<i> &gt;
  85 </I>&gt;<i> &gt;database/version4: Read error on exception.db
  86 </I>&gt;<i>
  87 </I>&gt;<i>      Can you send me an example database that has this problem?
  88 </I>
  89 Sent off-list.
  90
  91 Mark.
  92
  93
  94 </PRE>
  95
  96 <!--endarticle-->
  97     <HR>
  98     <P><UL>
  99         <!--threads-->
 100         <LI>Previous message: <A HREF="000183.html">[IRCServices Coding] Services 5.0 Miunor Bugs/glitches/suggestions
 101 </A></li>
 102         <LI>Next message: <A HREF="000184.html">[IRCServices Coding] Services 5.0 Bug in oper.db
 103 </A></li>
 104          <LI> <B>Messages sorted by:</B>
 105               <a href="date.html#185">[ date ]</a>
 106               <a href="thread.html#185">[ thread ]</a>
 107               <a href="subject.html#185">[ subject ]</a>
 108               <a href="author.html#185">[ author ]</a>
 109          </LI>
 110        </UL>
 111
 112 </body></html>