The peerblock.conf settings file could theoretically become corrupt, if
PeerBlock faults (or the machine shuts down or crashes) while writing your
settings out to that file.
What we should do is first write out settings to a peerblock.conf.temp
file, then rename peerblock.conf to peerblock.conf.old, then rename
peerblock.conf.temp to peerblock.conf. During startup, we should also put
in some recovery code in case we find during startup that the config-file
is corrupt.
Marking as low priority since we have no direct evidence that this has
actually happened, just a theory based on a reported problem...
Original issue reported on code.google.com by peerbloc...@gmail.com on 14 Oct 2009 at 11:05
Original issue reported on code.google.com by
peerbloc...@gmail.com
on 14 Oct 2009 at 11:05