Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: corrupted score files: "..." entries
Date: Thu, 30 Jan 2003 22:00:45 +0100	[thread overview]
Message-ID: <v9y952pd36.fsf@marauder.physik.uni-ulm.de> (raw)

Hi,

from time to time I noticed that my (main) score file gets corrupted.
It's happens very rarely (once in several weeks or months) and I don't
know how to reproduce it.

It's not a big problem for me (just copy the backup from yesterday),
but maybe someone has an idea?

Here's a shortened version of the diff between the backup file and the
corrupt one.  Note the bogus lines containing the string "...)":

--8<---------------cut here---------------start------------->8---
--- all.SCORE_yesterday	Tue Jan 28 20:16:55 2003
+++ all.SCORE_corrupt	Thu Jan 30 21:01:41 2003
@@ -14,24 +14,7 @@
   ("\"Eduardo Botelho\" <info@eduardobotelho.com>" -1000 nil e)
-  ("\"CROWDER NICK\" <crowdpub@mindspring.com>" -1000 nil e)
-  ("\"Promotions Manager\" <nationalmkt@planters.net>" -1000 nil e)
[...]
-  ("\"Mxxxxxx Xxxx\" <mxxxxxx.xxxx@xxxxx.xxxx-xxxxxx.xx>" -1 731231 s)
-  ("\"Plustech Automotive\" <plustech@citynet.co.kr>" -1000 nil e))
+  ...)
  ("references"
+  ("<200301301445.OAA21532@kaupp.chemie.uni-oldenburg.de>" nil 731245 s)
   ("<b15en2$8b3$1@mid.downhill.at.eu.org>" nil 731243 s)
-  ("<RfD-1-Loeschung-de.rec.sf.[...]-22.01.2003@dana.de>" -1000 731243 s)
+  ("<RfD-1-Loeschung-de.rec.sf.[...]-22.01.2003@dana.de>" -1000 731245 s)
   ("<b0hbdc$pccdr$3@ID-151041.news.dfncis.de>" nil 731238 s)
@@ -44,22 +27,10 @@
   ("<avt14q$15te$1@redenix.uni-muenster.de>" nil 731229 s)
-  ("<87znq589vk.fsf@pc201-37.biochem.uni-potsdam.de>" nil 731229 s)
-  ("<uvg0t1f1m.fsf@wanadoo.fr>" nil 731229 s)
-  ("<uy95ofavi.fsf@wanadoo.fr>" nil 731229 s)
[...]
-  ("<84isx69sxv.fsf@lucy.cs.uni-dortmund.de>" nil 731224 s)
-  ("<RfD-1-Einrichtung-de.newusers.misc-01.10.2002@dana.de>" -2 731234 s))
+  ...)
  ("subject"
   ("Archivexpert" -1000 731237 s)
-  ("reconsider defaults custom group" 2 731223 s)
-  ("urgent" -1000 731224 s)
+  ("urgent" -1000 731245 s)
   ("Charta von de.comp.os.unix.linux.moderated" -1000 731235 s)
-  ("<2002-05-03> Moderations [...] de.comp.hardware.announce" -1000 731239 s)
+  ("<2002-05-03> Moderations [...] de.comp.hardware.announce" -1000 731245 s)
   ("[Postingstatistik]" nil nil e)
-  ("[FAQ] Netscape, Mozilla -> de.comm.software.mozilla" -1000 731242 s)
+  ("[FAQ] Netscape, Mozilla -> de.comm.software.mozilla" -1000 731245 s)
   ("virus" -1 731241 s))
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/



             reply	other threads:[~2003-01-30 21:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30 21:00 Reiner Steib [this message]
2003-01-31  4:50 ` Katsumi Yamaoka
2003-01-31 13:41   ` Reiner Steib
2003-01-31 15:26     ` Katsumi Yamaoka
2003-01-31 16:09       ` Reiner Steib
2003-02-01 16:35   ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v9y952pd36.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).