Hi,

Here is what happens (I think) if E-log encounters a full file system where it keeps the user authorization file:

1. When a user connects, E-log will make a backup of the file. The backup will be corrupt since the file system is full.

2. E-log will modify the contents of the original file, and write it back. The file will be corrupt since the file system is full.

3. Now, both the backup and the normal file are corrupt and you cannot log on, until someone cleans up the file system and restores a valid copy of the file.

Would it be possible to fix this ? Like abort if step 1 is not successful. And restore the backup file if step 2 is not successful.

Thanks a lot for you help 

Soren