]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Nick Identification bug? | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Nick%20Identification%20bug%3F&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="001601.html"> | |
11 | <LINK REL="Next" HREF="001608.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Nick Identification bug?</H1> | |
15 | <B>Andrew Church</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Nick%20Identification%20bug%3F&In-Reply-To=" | |
17 | TITLE="[IRCServices] Nick Identification bug?">achurch at achurch.org | |
18 | </A><BR> | |
19 | <I>Mon Mar 12 00:52:01 PST 2001</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001601.html">[IRCServices] Nick Identification bug? | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001608.html">[IRCServices] Ideas , features | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1602">[ date ]</a> | |
27 | <a href="thread.html#1602">[ thread ]</a> | |
28 | <a href="subject.html#1602">[ subject ]</a> | |
29 | <a href="author.html#1602">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>><i>I'm wondering if this is a bug or something I might have missed in the | |
35 | </I>><i>configuration file (read over 3 times). | |
36 | </I>><i> | |
37 | </I>><i>CASE 1: | |
38 | </I>><i>--------- | |
39 | </I>><i> - Same IP, same username (identd), log into IRC, services will ask the | |
40 | </I>><i>user to identify if not it will disconnect or change nick. | |
41 | </I>><i> | |
42 | </I>><i>-NickServ- This nickname is registered and protected. If it is your | |
43 | </I>><i>-NickServ- nick, type /msg NickServ IDENTIFY password. Otherwise, | |
44 | </I>><i>-NickServ- please choose a different nick. | |
45 | </I>><i>-NickServ- If you do not change within one minute, I will change your | |
46 | </I>><i>nick. | |
47 | </I>><i> | |
48 | </I>><i> | |
49 | </I>><i>The same user gets disconnected, then attempts to reconnect back with | |
50 | </I>><i>the same IP/Username, Nickserv WILL NOT prompt the user with the | |
51 | </I>><i>message: | |
52 | </I> | |
53 | This should never happen with Dreamforge, Bahamut, and Unreal. | |
54 | With other servers, it can happen if the user disconnects from one | |
55 | server and connects to another one whose clock is slower, thus giving | |
56 | the user the same timestamp (if this is the case then either fix your | |
57 | servers' clocks [preferred] or enable NoSplitRecovery in services.conf). | |
58 | ||
59 | If you can confirm this happening in any other circumstances I | |
60 | would appreciate more detailed information. In particular, you should | |
61 | check whether the user actually has access to the nick in question or | |
62 | whether it's just a case of a message not being sent. | |
63 | ||
64 | ><i>CASE 2: | |
65 | </I>><i>-------------- | |
66 | </I>><i>If a nick is identified then changed to another un-registered nick, | |
67 | </I>><i>when doing /whois newnick the newnick is being reported by the server | |
68 | </I>><i>as being registered. I assume the mode +r was not being removed and | |
69 | </I>><i>I"m not sure if the job of removing +r is services job or ircd job. I | |
70 | </I>><i>ran services in -debug mode and see that the server does send the nick | |
71 | </I>><i>change to services but services doesn't send back to the server (ie | |
72 | </I>><i>mode -r on the nick) etc.. | |
73 | </I> | |
74 | According to comments in the code, Bahamut servers should | |
75 | automatically remove -r on nick change. If this is not the case let | |
76 | me know and I'll fix the code. | |
77 | ||
78 | For other servers, Services does send a -r when changing from a | |
79 | registered nick to an unregistered one. | |
80 | ||
81 | ><i>Feature Addition? | |
82 | </I>><i>------------------- | |
83 | </I>><i>I'm wondering if there is a feature for making ChanServ to join #'s if | |
84 | </I>><i>the owner wish the bot to stay in the channel? | |
85 | </I> | |
86 | No, and there will not be. See the FAQ. | |
87 | ||
88 | --Andrew Church | |
89 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | New address - please note. | |
90 | <A HREF="http://achurch.org/">http://achurch.org/</A> | メールアドレスが変わりました。 | |
91 | ||
92 | ||
93 | </PRE> | |
94 | ||
95 | <!--endarticle--> | |
96 | <HR> | |
97 | <P><UL> | |
98 | <!--threads--> | |
99 | <LI>Previous message: <A HREF="001601.html">[IRCServices] Nick Identification bug? | |
100 | </A></li> | |
101 | <LI>Next message: <A HREF="001608.html">[IRCServices] Ideas , features | |
102 | </A></li> | |
103 | <LI> <B>Messages sorted by:</B> | |
104 | <a href="date.html#1602">[ date ]</a> | |
105 | <a href="thread.html#1602">[ thread ]</a> | |
106 | <a href="subject.html#1602">[ subject ]</a> | |
107 | <a href="author.html#1602">[ author ]</a> | |
108 | </LI> | |
109 | </UL> | |
110 | ||
111 | </body></html> |