]> jfr.im git - irc.git/blame - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001117.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001117.html
CommitLineData
3bd189cb
JR
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2<HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Panic / Segmentation fault?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Panic%20/%20Segmentation%20fault%3F&In-Reply-To=3A664FA8.F32669F4%40bclark.yi.org">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001116.html">
11 <LINK REL="Next" HREF="001121.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Panic / Segmentation fault?</H1>
15 <B>ben at desync.com</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Panic%20/%20Segmentation%20fault%3F&In-Reply-To=3A664FA8.F32669F4%40bclark.yi.org"
17 TITLE="[IRCServices] Panic / Segmentation fault?">ben at desync.com
18 </A><BR>
19 <I>Wed Jan 17 19:18:42 PST 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001116.html">[IRCServices] Panic / Segmentation fault?
22</A></li>
23 <LI>Next message: <A HREF="001121.html">[IRCServices] Panic / Segmentation fault?
24</A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1117">[ date ]</a>
27 <a href="thread.html#1117">[ thread ]</a>
28 <a href="subject.html#1117">[ subject ]</a>
29 <a href="author.html#1117">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33<!--beginarticle-->
34<PRE>Being able to export the DBs like this would make it easy to write scripts that look up user info from a website or generate stats or whatever. I think that'd be pretty cool.
35
36-ben
37
38The Inside3D Network
39
40On Wed, Jan 17, 2001 at 09:06:32PM -0500, Bryan Clark wrote:
41&gt;<i> David Blanchard wrote:
42</I>&gt;<i>
43</I>&gt;<i> &gt; Here's an idea... Make a way to export the *.db to a ascii text file, and a
44</I>&gt;<i> &gt; way to import it in the event of database corruption. Rebuilding the text
45</I>&gt;<i> &gt; file would be much easier on the admin. Think of the way, for example, a
46</I>&gt;<i> &gt; program like AutoCad handles the source, and compiled versions of its menu
47</I>&gt;<i> &gt; files. This, coupled with the habit of regular backups, could really help
48</I>&gt;<i> &gt; out a lot. I could go on and on with why this a good idea, but for now I'll
49</I>&gt;<i> &gt; just let ya dwell on it :)
50</I>&gt;<i>
51</I>&gt;<i> That would probably be a Bad Thing (tm) if you don't use encrypted passwords,
52</I>&gt;<i> though. I just run backups every eight hours -- something which has already
53</I>&gt;<i> gotten me out of trouble once already ...... ;)
54</I>
55
56</PRE>
57
58<!--endarticle-->
59 <HR>
60 <P><UL>
61 <!--threads-->
62 <LI>Previous message: <A HREF="001116.html">[IRCServices] Panic / Segmentation fault?
63</A></li>
64 <LI>Next message: <A HREF="001121.html">[IRCServices] Panic / Segmentation fault?
65</A></li>
66 <LI> <B>Messages sorted by:</B>
67 <a href="date.html#1117">[ date ]</a>
68 <a href="thread.html#1117">[ thread ]</a>
69 <a href="subject.html#1117">[ subject ]</a>
70 <a href="author.html#1117">[ author ]</a>
71 </LI>
72 </UL>
73
74</body></html>