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] Re: backups | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20backups&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="000296.html"> | |
| 11 | <LINK REL="Next" HREF="000299.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] Re: backups</H1> | |
| 15 | <B>Chris</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20backups&In-Reply-To=" | |
| 17 | TITLE="[IRCServices] Re: backups">chriswh at cyberhighway.net | |
| 18 | </A><BR> | |
| 19 | <I>Sun Nov 7 11:44:08 PST 1999</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="000296.html">[IRCServices] (no subject) | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="000299.html">[IRCServices] Re: backups | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#298">[ date ]</a> | |
| 27 | <a href="thread.html#298">[ thread ]</a> | |
| 28 | <a href="subject.html#298">[ subject ]</a> | |
| 29 | <a href="author.html#298">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>I know this is not what you guys are looking for, but so you don't get a | |
| 35 | huge mess, you could try making something like DALnet's (or use to be). | |
| 36 | When main services go down, instead of worrying about making all this have | |
| 37 | to match(which could be a real pain) make a services link that would say | |
| 38 | that services are temporarily down and other nice stuff. This may be coded | |
| 39 | directly into the dalnet IRCD, as I think it is, because server's with no | |
| 40 | links whatsoever have this message. I don't know, just throwing in my | |
| 41 | worthless comments =) | |
| 42 | ||
| 43 | -Chris | |
| 44 | ||
| 45 | ---------- | |
| 46 | ><i> From: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">quension at softhome.net</A> | |
| 47 | </I>><i> To: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ender.shadowfire.org</A> | |
| 48 | </I>><i> Subject: [IRCServices] Re: backups | |
| 49 | </I>><i> Date: Saturday, November 06, 1999 4:05 PM | |
| 50 | </I>><i> | |
| 51 | </I>><i> zshack wrote: | |
| 52 | </I>><i> | |
| 53 | </I>><i> > It says something in the readme that it can be done. I have 2 sets of | |
| 54 | </I>><i> > services linked, but when the primary fails the secondary set stays in | |
| 55 | </I>><i> > read only. I was under the impression that the second set would "take | |
| 56 | </I>><i> > over" unless there is a certain command i can give it to start when the | |
| 57 | </I>><i> > primary fails. | |
| 58 | </I>><i> | |
| 59 | </I>><i> The secondary set would have to stay in read-only unless you are able to | |
| 60 | </I>><i> easily sync the dbs in the opposite direction (from backup to primary) as | |
| 61 | </I>><i> well. And if the backup and primary services are on separate sections of | |
| 62 | </I>><i> the network, a network split would cause a nice mess of confusion as | |
| 63 | </I>users | |
| 64 | ><i> change things on the backup services that are not echoed to the primary. | |
| 65 | </I>><i> | |
| 66 | </I>><i> I've done some thinking recently as to what a really good backup system | |
| 67 | </I>><i> would look like, and have come to the conclusion that it's going to take | |
| 68 | </I>a | |
| 69 | ><i> rather large amount of work. | |
| 70 | </I>><i> | |
| 71 | </I>><i> If you still want to run the backups as full services, OperServ's SET | |
| 72 | </I>><i> READONLY OFF may work. | |
| 73 | </I>><i> | |
| 74 | </I>><i> I would like to know how you've set up the backups... are they using | |
| 75 | </I>><i> different nicks? | |
| 76 | </I>><i> | |
| 77 | </I>><i> -- Quension | |
| 78 | </I>><i> | |
| 79 | </I>><i> --------------------------------------------------------------- | |
| 80 | </I>><i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A> | |
| 81 | </I>><i> with "unsubscribe ircservices" in the body, without the quotes. | |
| 82 | </I>--------------------------------------------------------------- | |
| 83 | To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A> | |
| 84 | with "unsubscribe ircservices" in the body, without the quotes. | |
| 85 | ||
| 86 | </PRE> | |
| 87 | ||
| 88 | <!--endarticle--> | |
| 89 | <HR> | |
| 90 | <P><UL> | |
| 91 | <!--threads--> | |
| 92 | <LI>Previous message: <A HREF="000296.html">[IRCServices] (no subject) | |
| 93 | </A></li> | |
| 94 | <LI>Next message: <A HREF="000299.html">[IRCServices] Re: backups | |
| 95 | </A></li> | |
| 96 | <LI> <B>Messages sorted by:</B> | |
| 97 | <a href="date.html#298">[ date ]</a> | |
| 98 | <a href="thread.html#298">[ thread ]</a> | |
| 99 | <a href="subject.html#298">[ subject ]</a> | |
| 100 | <a href="author.html#298">[ author ]</a> | |
| 101 | </LI> | |
| 102 | </UL> | |
| 103 | ||
| 104 | </body></html> |