Re: Exim spool structure and fsck

Páxina inicial
Borrar esta mensaxe
Responder a esta mensaxe
Autor: Philip Hazel
Data:  
Para: Piete Brooks
CC: Chris Thompson, exim-users
Asunto: Re: Exim spool structure and fsck
On Mon, 16 Sep 1996, Piete Brooks wrote:

> > Of course, exim's scheme of double /input files has a lot going for it
> > in other respects. Is this sort of repair job just something one has to
> > give up as a consequence? Has anyone had any interesting disk crashes while
> > running exim, and what were they able to do?
>
> The *-H and msglog/ files could easily have the ID included in them,
> [[ not *really* needed, as the msglog/ file has the Message-ID ]]
> but as the *-D cannot, one would have to make do with the the inode info
> (inode number, date, size, ...) and a `sum' of the *-D in the *-H


There's no reason why the -D file couldn't have the ID as its first
line. Exim would just not send it when transporting the message. I have
noted this idea.


--
Philip Hazel                   University Computing Service,
ph10@???             New Museums Site, Cambridge CB2 3QG,
P.Hazel@???          England.  Phone: +44 1223 334714