software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001115.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="001111.html">
  11    <LINK REL="Next"  HREF="001116.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Panic / Segmentation fault?</H1>
  15     <B>David Blanchard</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?">dblanch at home.com
  18        </A><BR>
  19     <I>Wed Jan 17 17:52:16 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001111.html">[IRCServices] Panic / Segmentation fault?
  22 </A></li>
  23         <LI>Next message: <A HREF="001116.html">[IRCServices] Panic / Segmentation fault?
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1115">[ date ]</a>
  27               <a href="thread.html#1115">[ thread ]</a>
  28               <a href="subject.html#1115">[ subject ]</a>
  29               <a href="author.html#1115">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Here's an idea... Make a way to export the *.db to a ascii text file, and a
  35 way to import it in the event of database corruption.  Rebuilding the text
  36 file would be much easier on the admin.  Think of the way, for example, a
  37 program like AutoCad handles the source, and compiled versions of its menu
  38 files.  This, coupled with the habit of regular backups, could really help
  39 out a lot.  I could go on and on with why this a good idea, but for now I'll
  40 just let ya dwell on it :)
  41
  42 My 1.5 cents... lol
  43
  44 David
  45
  46 &gt;<i>      Actually, I'm considering a fairly major change in the database
  47 </I>&gt;<i> format for 5.0 (my plan is to start 5.0 development shortly after
  48 </I>&gt;<i> releasing 4.5) to prevent this kind of problem, where a single corrupt
  49 </I>&gt;<i> entry renders the entire database unusable.  However, the DBs shouldn't
  50 </I>&gt;<i> become corrupt in the first place, so the only real solution I can
  51 </I>&gt;<i> suggest is to take backups.  On EsperNet we take two backups a day so
  52 </I>&gt;<i> we're never more than 12 hours behind, which should be more than enough.
  53 </I>&gt;<i> (Why would recovering from a previous day's backup not be an option?
  54 </I>&gt;<i> It's surely better than losing everything.)
  55 </I>&gt;<i>
  56 </I>
  57
  58
  59
  60 </PRE>
  61
  62 <!--endarticle-->
  63     <HR>
  64     <P><UL>
  65         <!--threads-->
  66         <LI>Previous message: <A HREF="001111.html">[IRCServices] Panic / Segmentation fault?
  67 </A></li>
  68         <LI>Next message: <A HREF="001116.html">[IRCServices] Panic / Segmentation fault?
  69 </A></li>
  70          <LI> <B>Messages sorted by:</B>
  71               <a href="date.html#1115">[ date ]</a>
  72               <a href="thread.html#1115">[ thread ]</a>
  73               <a href="subject.html#1115">[ subject ]</a>
  74               <a href="author.html#1115">[ author ]</a>
  75          </LI>
  76        </UL>
  77
  78 </body></html>