[[AfZ]PiMp J]

not that i've found yet. temp solution is to just not reboot it much and to make a backup copy of it so when it reboots you only have to restore the backup.

..edit..as an idea, if you could either 1) just set proftpd.conf to be unwritable even to root (is that possible?) or 2) rename it to proftpd.conf.real or whatever and delete proftpd.conf, then create an alias/link called proftpd.conf and link it to proftpd.conf.real. Then set proftpd.conf (the link) to not be writable (if possible)

figuring that way you could modify the real file without having to make it writable each time, and that the OS would be too stupid to overwrite your .real file, and it would hopefully fail to overwrite the proftpd.conf link with some sort of default file

if all of that fails, then perhaps blu is totally correct on the subject (which would SUCK, since it defeats all things known as possible in my mind) in that he mentioned the OS being setup as some sort of uber raid1, copied to all drives type deal (real technical in my explanation, i know heh) and that the ugly stepchild gets the shaft and has its different files overwritten since it's outweighed 3 to 1. This is somehow on top of the raid5 or whatever raid setup you chose for the storage.