--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [IRCServices] ChanServ refuses to KEEPTOPIC and TOPICLOCK .
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20refuses%20to%20KEEPTOPIC%20%20and%20TOPICLOCK%20.&In-Reply-To=">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001152.html">
+ <LINK REL="Next" HREF="001156.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[IRCServices] ChanServ refuses to KEEPTOPIC and TOPICLOCK .</H1>
+ <B>David Blanchard</B>
+ <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20refuses%20to%20KEEPTOPIC%20%20and%20TOPICLOCK%20.&In-Reply-To="
+ TITLE="[IRCServices] ChanServ refuses to KEEPTOPIC and TOPICLOCK .">dblanch at home.com
+ </A><BR>
+ <I>Sun Jan 21 12:45:17 PST 2001</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001152.html">[IRCServices] ChanServ refuses to KEEPTOPIC and TOPICLOCK .
+</A></li>
+ <LI>Next message: <A HREF="001156.html">[IRCServices] ChanServ refuses to KEEPTOPIC and TOPICLOCK .
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1153">[ date ]</a>
+ <a href="thread.html#1153">[ thread ]</a>
+ <a href="subject.html#1153">[ subject ]</a>
+ <a href="author.html#1153">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Well, I haven't seen too much bad there, except I can still change the topic
+on the channel even with topiclock on (although when I exit and re-enter
+channel, the /cs set # topic one come back up) We use v4.4.8 of services and
+Unreal 3.1.1Darkshades. No real compatibility probs, rather just missing
+features that I needed added to the MLOCK... (i.e. A, S, N, and G channel
+flags) Actually, there is that thing that memoserv doesn't seem to do
+correctly with doing a #channel send (or perhaps just isn't finished?), but
+I just wrote a csend function for it instead (ala StarChat's)
+
+David
+
+><i> I have a similar setup (as I've said previously). We've been running
+</I>><i> ircservices with unreal ircd for about 2 years. The problem didn't come up
+</I>><i> until we upgraded to 4.4.8 and unreal 3.0 (but we did that at the same
+</I>time
+><i> so I don't know which started it). Up to now we just left it there and
+</I>dealt
+><i> with it, but we are getting more and more complaints now. One user
+</I>couldn't
+><i> register a channel even though he was opped (actually, it was an oper on
+</I>our
+><i> server, so he wans't completely stupid about how to do it). It seems it
+</I>may
+><i> be compatibility issues with unreal moreso than a ircservices problem, but
+</I>><i> it'd be nice if it'd work right. I'll be emailing the unreal list with
+</I>this
+><i> info as well.
+</I>><i>
+</I>
+
+
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001152.html">[IRCServices] ChanServ refuses to KEEPTOPIC and TOPICLOCK .
+</A></li>
+ <LI>Next message: <A HREF="001156.html">[IRCServices] ChanServ refuses to KEEPTOPIC and TOPICLOCK .
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1153">[ date ]</a>
+ <a href="thread.html#1153">[ thread ]</a>
+ <a href="subject.html#1153">[ subject ]</a>
+ <a href="author.html#1153">[ author ]</a>
+ </LI>
+ </UL>
+
+</body></html>