]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] session limit bug | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20session%20limit%20bug&In-Reply-To=200303241814.h2OIEXV11701%40localhost.localdomain"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="002000.html"> | |
11 | <LINK REL="Next" HREF="001995.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] session limit bug</H1> | |
15 | <B>Gastaman</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20session%20limit%20bug&In-Reply-To=200303241814.h2OIEXV11701%40localhost.localdomain" | |
17 | TITLE="[IRCServices Coding] session limit bug">gastaman at azzurra.org | |
18 | </A><BR> | |
19 | <I>Mon Mar 24 10:28:23 PST 2003</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="002000.html">AW: [IRCServices Coding] session limit bug | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001995.html">[IRCServices Coding] session limit bug | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1994">[ date ]</a> | |
27 | <a href="thread.html#1994">[ thread ]</a> | |
28 | <a href="subject.html#1994">[ subject ]</a> | |
29 | <a href="author.html#1994">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>It was 06:14 PM 3/24/2003 +0000 when Craig Edwards came up | |
35 | with: | |
36 | ><i>Is there a way to keep services in sync if its desynced, by | |
37 | </I>><i>resyncing it at fixed intervals? This would not only fix | |
38 | </I>><i>problems caused by (ab)use of operserv raw, but would also fix | |
39 | </I>><i>problems caused in other ways (ive had a couple of desyncs | |
40 | </I>><i>before caused by buggy server software etc) - it could be set | |
41 | </I>><i>from config to say resync once every 24h or once every week or | |
42 | </I>><i>whenever the admin prefers, by simulating a form of "warm | |
43 | </I>><i>reboot" where it could somehow retrieve all network | |
44 | </I>><i>information again from the uplink and redo its lists from | |
45 | </I>><i>scratch, kinda like a rehash.... or maybe do this on /os | |
46 | </I>><i>rehash if a commandline option is given? Just an idea... | |
47 | </I> | |
48 | Not if the ircd doesn't support it, and as far | |
49 | as I know none does (certainly not Bahamut, | |
50 | any version), unless you squit and reconnect. | |
51 | ||
52 | And besides, use of the RAW command is not | |
53 | recommended for the very reason it can lead | |
54 | to desynchs, and IMHO any services should not | |
55 | waste time/cpu/memory/whatever to try and | |
56 | fix input errors, it should be left to whoever | |
57 | inputs the wrong commands to refrain from | |
58 | doing so. | |
59 | ||
60 | As for buggy server software (are you running | |
61 | Unreal? =P), bugs should be fixed on the server's | |
62 | side, not on the services' if they do their job. | |
63 | ||
64 | ||
65 | </PRE> | |
66 | ||
67 | <!--endarticle--> | |
68 | <HR> | |
69 | <P><UL> | |
70 | <!--threads--> | |
71 | <LI>Previous message: <A HREF="002000.html">AW: [IRCServices Coding] session limit bug | |
72 | </A></li> | |
73 | <LI>Next message: <A HREF="001995.html">[IRCServices Coding] session limit bug | |
74 | </A></li> | |
75 | <LI> <B>Messages sorted by:</B> | |
76 | <a href="date.html#1994">[ date ]</a> | |
77 | <a href="thread.html#1994">[ thread ]</a> | |
78 | <a href="subject.html#1994">[ subject ]</a> | |
79 | <a href="author.html#1994">[ author ]</a> | |
80 | </LI> | |
81 | </UL> | |
82 | ||
83 | </body></html> |