Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   User authorization file corruption, posted by soren poulsen on Fri Sep 18 07:39:02 2009 
    icon2.gif   Re: User authorization file corruption, posted by Stefan Ritt on Fri Oct 16 12:17:15 2009 
       icon2.gif   Re: User authorization file corruption, posted by soren poulsen on Mon Oct 26 10:15:20 2009 
Message ID: 66565     Entry time: Mon Oct 26 10:15:20 2009     In reply to: 66560
Icon: Reply  Author: soren poulsen  Author Email: soren.poulsen@cern.ch 
Category: Bug report  OS: Linux  ELOG Version: 2.7.7 
Subject: Re: User authorization file corruption 

Stefan Ritt wrote:

soren poulsen wrote:

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

Ok, I finally found some time (I'm pretty busy these days) to add a check for a potential full file system in SVN revision 2258. So before the password file would get corrupted, elog shows an error message about the full file system and just stops to work until space is freed up. 

Great. We fully appreciate that your are busy (with other things than E-log).

Thanks for the resolution.

Soren

ELOG V3.1.5-3fb85fa6