]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/002522.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 002522.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> AW: AW: AW: [IRCServices] Backup databases?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20AW%3A%20AW%3A%20%5BIRCServices%5D%20Backup%20databases%3F&In-Reply-To=163833225394.20011114075854%40groth.net">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="002515.html">
11 <LINK REL="Next" HREF="002523.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>AW: AW: AW: [IRCServices] Backup databases?</H1>
15 <B>Josh</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20AW%3A%20AW%3A%20%5BIRCServices%5D%20Backup%20databases%3F&In-Reply-To=163833225394.20011114075854%40groth.net"
17 TITLE="AW: AW: AW: [IRCServices] Backup databases?">grenday288 at geocities.com
18 </A><BR>
19 <I>Wed Nov 14 14:52:00 PST 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002515.html">AW: AW: AW: [IRCServices] Backup databases?
22 </A></li>
23 <LI>Next message: <A HREF="002523.html">AW: AW: AW: [IRCServices] Backup databases?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2522">[ date ]</a>
27 <a href="thread.html#2522">[ thread ]</a>
28 <a href="subject.html#2522">[ subject ]</a>
29 <a href="author.html#2522">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>On 14 Nov 2001, at 7:58, Duane Groth wrote:
35
36 Its easier having 1 set of services on a really stable box that never
37 goes down.. but thats only possible if you only have a few or just
38 yourself knowing the ip to the hub and keep it that way by only
39 adding c/n's to a couple other hubs and never link client servers
40 directly to it. we have this setup on my net and it works well.
41
42 (services hub ircd:)
43 Server Up 169 days, 11:23:14
44
45 &gt;<i> Hello Georges,
46 </I>&gt;<i>
47 </I>&gt;<i> As I said originally, I would like to see this feature purely for a
48 </I>&gt;<i> redundancy point of view, as I have a reasonably setup IRC network,
49 </I>&gt;<i> the DNS probes the IRC servers and removes dead server
50 </I>&gt;<i> automatically, I have the IRC servers each setup with multiple hubs,
51 </I>&gt;<i> so in the event of any one hub dying there is redundancy to keep the
52 </I>&gt;<i> network together, however I am unable to think of a suitable way of
53 </I>&gt;<i> making services redundant, and in the event of failure of the
54 </I>&gt;<i> primary server that it's linking into the network with, for whatever
55 </I>&gt;<i> reason, a secondary will kick in, with read only, so that people can
56 </I>&gt;<i> authenticate, but not change details, this is the only single point
57 </I>&gt;<i> of failure on my network that requires manual intervention.
58 </I>&gt;<i>
59 </I>&gt;<i> --
60 </I>&gt;<i> Best regards,
61 </I>&gt;<i> Duane mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">duane at groth.net</A>
62 </I>&gt;<i>
63 </I>&gt;<i> Wednesday, November 14, 2001, 7:45:01 AM, you wrote:
64 </I>&gt;<i>
65 </I>&gt;<i> GB&gt; I like the idea of managing nicks through the browser, which is very much
66 </I>&gt;<i> GB&gt; more intuitive for many users who have no knowledge about IRC and only know
67 </I>&gt;<i> GB&gt; that they can type text into their client.
68 </I>&gt;<i> GB&gt; It is really intresting for very small networks who pretend to have a
69 </I>&gt;<i> GB&gt; 'community'. People will be able to share much more information when
70 </I>&gt;<i> GB&gt; registering their nick on the web. This registration can be passed on to
71 </I>&gt;<i> GB&gt; nickserv who uses the same information than in the Userinfo Database on the
72 </I>&gt;<i> GB&gt; web.
73 </I>&gt;<i> GB&gt; People will even be able to change their IRC-Settings in their browser.
74 </I>&gt;<i>
75 </I>&gt;<i> GB&gt; It took me quite a number of hours to hack something like this into services
76 </I>&gt;<i> GB&gt; though, so I would appreciate if there was a possibility (i.e. interface) to
77 </I>&gt;<i> GB&gt; re-organise all this and make it a little more structured.
78 </I>&gt;<i>
79 </I>&gt;<i> GB&gt; Georges
80 </I>&gt;<i>
81 </I>&gt;<i> GB&gt; -----Ursprungliche Nachricht-----
82 </I>&gt;<i> GB&gt; Von: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-admin at ircservices.za.net</A>
83 </I>&gt;<i> GB&gt; [mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-admin at ircservices.za.net</A>]Im Auftrag von Craig McLure
84 </I>&gt;<i> GB&gt; Gesendet: Dienstag, 13. November 2001 21:28
85 </I>&gt;<i> GB&gt; An: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>
86 </I>&gt;<i> GB&gt; Betreff: RE: AW: AW: [IRCServices] Backup databases?
87 </I>&gt;<i>
88 </I>&gt;<i>
89 </I>&gt;<i> GB&gt; Lol..
90 </I>&gt;<i> GB&gt; MySQL, does that mean ppl will be able to reg nicks and manage nicks in
91 </I>&gt;<i> GB&gt; their web browser?
92 </I>&gt;<i> GB&gt; Interesting concept :P
93 </I>&gt;<i> GB&gt; But wouldn't that mean pw encryption?
94 </I>&gt;<i>
95 </I>&gt;<i> GB&gt; -----Original Message-----
96 </I>&gt;<i> GB&gt; From: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-admin at ircservices.za.net</A>
97 </I>&gt;<i> GB&gt; [mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-admin at ircservices.za.net</A>] On Behalf Of Duane Groth
98 </I>&gt;<i> GB&gt; Sent: 13 November 2001 20:08
99 </I>&gt;<i> GB&gt; To: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>
100 </I>&gt;<i> GB&gt; Subject: Re: AW: AW: [IRCServices] Backup databases?
101 </I>&gt;<i>
102 </I>&gt;<i> GB&gt; Hello,
103 </I>&gt;<i>
104 </I>&gt;<i> GB&gt; No, but have the option of choosing MySQL for database, or using
105 </I>&gt;<i> GB&gt; it's own flat file format, the side benefit from this would be easier
106 </I>&gt;<i> GB&gt; web interfaces with PHP and the like, this unlike some simple
107 </I>&gt;<i> GB&gt; scripting has to be done in services itself. You should be using scp
108 </I>&gt;<i> GB&gt; or
109 </I>&gt;<i> GB&gt; similar for the remote archiving anyway, if you employ RSA/DSA keys
110 </I>&gt;<i> GB&gt; it's 1000x more secure, not to mention easier to script, hell you
111 </I>&gt;<i> GB&gt; can even setup your remote script to trigger tar/bzip, then the next
112 </I>&gt;<i> GB&gt; line to scp it off, so that you don't need to have 2 cron processes
113 </I>&gt;<i> GB&gt; going.
114 </I>&gt;<i>
115 </I>&gt;<i> GB&gt; --
116 </I>&gt;<i> GB&gt; Best regards,
117 </I>&gt;<i> GB&gt; Duane mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">duane at groth.net</A>
118 </I>&gt;<i>
119 </I>&gt;<i> GB&gt; Wednesday, November 14, 2001, 6:58:11 AM, you wrote:
120 </I>&gt;<i>
121 </I>&gt;<i> GB&gt;&gt; Re,
122 </I>&gt;<i>
123 </I>&gt;<i> GB&gt;&gt; well, MySQL support is nice, but not really suitable for everybody
124 </I>&gt;<i> GB&gt; (e.g.
125 </I>&gt;<i> GB&gt;&gt; users that don't have a MySQL account). The FTP-Upload thing would
126 </I>&gt;<i> GB&gt; probably
127 </I>&gt;<i> GB&gt;&gt; do the job for most people.
128 </I>&gt;<i>
129 </I>&gt;<i> GB&gt; -----------------------------------------------------------
130 </I>&gt;<i> GB&gt; To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
131 </I>&gt;<i> GB&gt; with the word UNSUBSCRIBE in the subject of the mail.
132 </I>&gt;<i> GB&gt; <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
133 </I>&gt;<i> GB&gt; -----------------------------------------------------------
134 </I>&gt;<i> GB&gt; To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
135 </I>&gt;<i> GB&gt; with the word UNSUBSCRIBE in the subject of the mail.
136 </I>&gt;<i> GB&gt; <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
137 </I>&gt;<i>
138 </I>&gt;<i> GB&gt; -----------------------------------------------------------
139 </I>&gt;<i> GB&gt; To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
140 </I>&gt;<i> GB&gt; with the word UNSUBSCRIBE in the subject of the mail.
141 </I>&gt;<i> GB&gt; <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
142 </I>&gt;<i>
143 </I>&gt;<i> -----------------------------------------------------------
144 </I>&gt;<i> To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
145 </I>&gt;<i> with the word UNSUBSCRIBE in the subject of the mail.
146 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
147 </I>
148
149 -------------------------------------
150 -- Josh Kirkorian [aka Poison-X]
151 -- Administrator - irc.insiderz.net
152
153 C Code. C code run. Run, code, run...
154 Segmentation fault (core dumped).. aww shit
155
156 </PRE>
157
158 <!--endarticle-->
159 <HR>
160 <P><UL>
161 <!--threads-->
162 <LI>Previous message: <A HREF="002515.html">AW: AW: AW: [IRCServices] Backup databases?
163 </A></li>
164 <LI>Next message: <A HREF="002523.html">AW: AW: AW: [IRCServices] Backup databases?
165 </A></li>
166 <LI> <B>Messages sorted by:</B>
167 <a href="date.html#2522">[ date ]</a>
168 <a href="thread.html#2522">[ thread ]</a>
169 <a href="subject.html#2522">[ subject ]</a>
170 <a href="author.html#2522">[ author ]</a>
171 </LI>
172 </UL>
173
174 </body></html>