software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001122.html

   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=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001114.html">
  11    <LINK REL="Next"  HREF="001123.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Panic / Segmentation fault?</H1>
  15     <B>Dr. K. Hawkes</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Panic%20/%20Segmentation%20fault%3F&In-Reply-To="
  17        TITLE="[IRCServices] Panic / Segmentation fault?">k.hawkes at zombies.force9.net
  18        </A><BR>
  19     <I>Thu Jan 18 13:31:52 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001114.html">[IRCServices] Channel suspension
  22 </A></li>
  23         <LI>Next message: <A HREF="001123.html">[IRCServices] Panic / Segmentation fault?
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1122">[ date ]</a>
  27               <a href="thread.html#1122">[ thread ]</a>
  28               <a href="subject.html#1122">[ subject ]</a>
  29               <a href="author.html#1122">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>[SNIP]
  35 &gt;<i>
  36 </I>&gt;<i> Here's an idea... Make a way to export the *.db to a ascii text file, and
  37 </I>a
  38 &gt;<i> way to import it in the event of database corruption.  Rebuilding the
  39 </I>text
  40 &gt;<i> file would be much easier on the admin.  Think of the way, for example, a
  41 </I>&gt;<i> program like AutoCad handles the source, and compiled versions of its
  42 </I>menu
  43 &gt;<i> files.  This, coupled with the habit of regular backups, could really
  44 </I>help
  45 &gt;<i> out a lot.  I could go on and on with why this a good idea, but for now
  46 </I>I'll
  47 &gt;<i> just let ya dwell on it :)
  48 </I>&gt;<i>
  49 </I>&gt;<i> My 1.5 cents... lol
  50 </I>&gt;<i>
  51 </I>&gt;<i> David
  52 </I>&gt;<i>
  53 </I>
  54 I must say this is a bad idea for DB's with unencrypted passwords, but
  55 apart from that I like that idea, would save me alot of pain and worry, my
  56 backups are a cron'd FTP to a remote location.  Although for some odd
  57 reason, the DB's don't like going to the remote location and seem
  58 corrupted, this is being worked on ATM.
  59
  60 But exporting the DB's to text would be nice, and the ability to re-import
  61 them again would be good.
  62
  63 That DB verification thing too, so the DB loads even if it has a corrupt
  64 entry would be a godsend, combine that with the export/import (so you could
  65 clean up the said entry manually perhaps?) would kick-ass IMHO.
  66
  67 Maybe a Conf option to allow EXPORT/IMPORT of DB's and to allow Automatic
  68 repair (if possible) of corrupt DB's to a minimum level anyhow???
  69
  70 Just my 0.2p.
  71
  72 Quinn
  73
  74
  75 </PRE>
  76
  77 <!--endarticle-->
  78     <HR>
  79     <P><UL>
  80         <!--threads-->
  81         <LI>Previous message: <A HREF="001114.html">[IRCServices] Channel suspension
  82 </A></li>
  83         <LI>Next message: <A HREF="001123.html">[IRCServices] Panic / Segmentation fault?
  84 </A></li>
  85          <LI> <B>Messages sorted by:</B>
  86               <a href="date.html#1122">[ date ]</a>
  87               <a href="thread.html#1122">[ thread ]</a>
  88               <a href="subject.html#1122">[ subject ]</a>
  89               <a href="author.html#1122">[ author ]</a>
  90          </LI>
  91        </UL>
  92
  93 </body></html>