I guess its time to develop some tacticts to improve our non-bdb file reliability; aka Netconfigs, citadel.control and citadel.config
possible errors... :
1) running out of disk space
2) crashing while writing
3) writing corrupted values
4) deffective disk
I guess 1 can be circumvented by allocating a bigger block on the disk then we actualy need; and if we need expansion, first expand the file, and then overwrite the contend we had in there before so the actual file stays valid as long as possible.
2) could be circumvented by writing on another file than we read, and then swap the actual files
3) is a little more of a problem. corruption is next of undetectable by humans in binary written value;
4) oh man...
next, the numbers in citadel.control grow in a rather different speed then the bdb version, room number, usernumber, fulltext indexed number; maybe it would be a good approach to seperate it from the other numbers?
looking at the message number, and slowing it down... maybe we could use the primary number file growing in 4k steps, and have a 4k big file where we X every next number taken?
