yarnpack and the unsync

From: Tim Middleton (hello-yarners@see.my.sig)
Date: Tue, 14 Jan 1997 18:27:18 -0500

It finally has happened to me as well. Just got that wacky Expire error,
and then run Yarnpack /i and it gives the (poorly named) "unsynced history"
error.

Yarnpack /i, at that time, reported 4920 message ID's in the history.pag,
while nnign reports there are only 4792 messages active... a difference of
128 messages.

Somehow, somewhere, Expire (it seems) is leaving in these extra MSG id's in
the history.pag -- now whether it is displaying this odd behavior because
of something Yarnpack did, or for some other reason, I still have no idea.

Of course I may have a fundimental misunderstanding of the history.pag.
Maybe it's a normal condition sometimes for it, and it leaves extra
previously expired msg ID's in there pointing to existing free space
blocks... dunno. A mystery... (-: Maybe all this confusion will motivate
Chin to write a pack-in place option. (-:

The good news is that this doesn't appear to be a serious problem (so far).
Rebuild -h, while it takes a bit of time, and resets all the import dates,
doesn't take much disk space to do and fixes it. No data is lost (as far as
I can tell, so far).

-- 
 ,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,_,
  Tim Moddletin =-= with love and a banana fish =-= as544 torfree.net
  -=-=-= read Macbeth by William Shakespeare, scary stuff kids =-=-=-
 ~`~`~'~`~`~'~`~`~'~`~`~'~`~`~'~`~`~'~`~'~'~`~'~'~`~'~'~`~'~'~`~'~'~`~
    Yarn/2 Bells & Whistles Page: http://www.io.org/~tm/bells2.html
        * January 14th * International Day of my Favorite Novel