Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 681 of 808  Not logged in ELOG logo
    icon2.gif   Re: Change / List Change doen't work anymore?, posted by Stefan Ritt on Thu Sep 17 18:32:59 2009 
[quote="Holger Mundhahs"]Hello @all,

I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my
icon4.gif   User authorization file corruption, posted by soren poulsen on Fri Sep 18 07:39:02 2009 
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.
    icon2.gif   Re: User authorization file corruption, posted by Stefan Ritt on Fri Oct 16 12:17:15 2009 


    
        
            soren poulsen wrote:
        
        
            
            Hi,
icon5.gif   "Collapse to last = 1" problem when reply twice to the same entry, posted by Gabriele Sirri on Sat Oct 24 01:10:24 2009 
Hello.

Please look at the entry 66525 of this forum (just 5 thread before this one):
    icon2.gif   Re: User authorization file corruption, posted by soren poulsen on Mon Oct 26 10:15:20 2009 


    
        
            Stefan Ritt wrote:
        
        
            
            
            
icon13.gif   elog crashes with a long thread., posted by David Pilgram on Thu Oct 29 20:48:41 2009 
Hi Stefan,

I have a thread of 70 entries.  I added another entry, which was saved, but elog crashed.
icon5.gif   2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Mon Nov 2 21:23:38 2009 
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that
it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations"
Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems
    icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Stefan Ritt on Tue Nov 3 09:04:34 2009 


    
        
            David Spindler wrote:
        
        
            
            I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no
ELOG V3.1.5-3fb85fa6