projects / irc.git / blame
| 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="001990.html"> | |
| 11 | <LINK REL="Next" HREF="001992.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] session limit bug</H1> | |
| 15 | <B>RT.Mail at verizon.net</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">RT.Mail at verizon.net | |
| 18 | </A><BR> | |
| 19 | <I>Mon Mar 24 10:15:14 PST 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="001990.html">[IRCServices Coding] session limit bug | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="001992.html">AW: [IRCServices Coding] session limit bug | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#1991">[ date ]</a> | |
| 27 | <a href="thread.html#1991">[ thread ]</a> | |
| 28 | <a href="subject.html#1991">[ subject ]</a> | |
| 29 | <a href="author.html#1991">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>That would be nice if that could be done at an interval the admin defines. | |
| 35 | ||
| 36 | < >On Mon, 24 Mar 2003 18:14:25 +0000, Craig Edwards wrote: | |
| 37 | < > know people will probably ignore or shoot down this request | |
| 38 | < > but, here goes.... | |
| 39 | < > | |
| 40 | < > Is there a way to keep services in sync if its desynced, by | |
| 41 | < > resyncing it at fixed intervals? This would not only fix | |
| 42 | < > problems caused by (ab)use of operserv raw, but would also fix | |
| 43 | < > problems caused in other ways (ive had a couple | |
| 44 | < > of desyncs before caused by buggy server software etc) - it | |
| 45 | < > could be set from config to say resync once every 24h | |
| 46 | < > or once every week or whenever the admin prefers, by simulating | |
| 47 | < > a form of "warm reboot" where it could somehow | |
| 48 | < > retrieve all network information again from the uplink and redo | |
| 49 | < > its lists from scratch, kinda like a rehash.... or | |
| 50 | < > maybe do this on /os rehash if a commandline option is given? | |
| 51 | < > Just an idea... | |
| 52 | ||
| 53 | ||
| 54 | ||
| 55 | </PRE> | |
| 56 | ||
| 57 | <!--endarticle--> | |
| 58 | <HR> | |
| 59 | <P><UL> | |
| 60 | <!--threads--> | |
| 61 | <LI>Previous message: <A HREF="001990.html">[IRCServices Coding] session limit bug | |
| 62 | </A></li> | |
| 63 | <LI>Next message: <A HREF="001992.html">AW: [IRCServices Coding] session limit bug | |
| 64 | </A></li> | |
| 65 | <LI> <B>Messages sorted by:</B> | |
| 66 | <a href="date.html#1991">[ date ]</a> | |
| 67 | <a href="thread.html#1991">[ thread ]</a> | |
| 68 | <a href="subject.html#1991">[ subject ]</a> | |
| 69 | <a href="author.html#1991">[ author ]</a> | |
| 70 | </LI> | |
| 71 | </UL> | |
| 72 | ||
| 73 | </body></html> |