Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 335 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown Text Attachments
  69782   Mon Apr 15 17:50:20 2024 Reply Stefan RittHastefan.ritt@psi.chBug reportWindowsELOG V3.1.3-793Re: Record date isn't set to current date when replying to elogsHave you tried the config option "Preset
on reply <attribute> = $date".
On a reply, the <attribute> will be
  
  67211   Wed Mar 14 14:45:23 2012 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.6Re: Record Proliferation

    

       
            
  
  67213   Wed Mar 14 15:34:41 2012 Question David PilgramDavid.Pilgram@epost.org.ukBug reportLinux | Windows2.7.6Re: Record Proliferation

    
        
  
  69146   Sun May 3 18:05:32 2020 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi,

I've had problems in the past
due to a dodgy pointer creating branches
  
  69147   Sun May 3 22:43:12 2020 Reply Frank Baptistacaffeinejazz@gmail.comQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi David,

Thanks for the quick response! 
Well, I'd have to say that the sequence
 200428a.log 
  69148   Mon May 4 14:55:53 2020 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi Frank,

There are two interesting points
about the log file. 
  
  69151   Fri May 22 21:03:05 2020 Reply Frank Baptistacaffeinejazz@gmail.comQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi David,

Well, you've made some very
interesting observations, and raised some
  
  69152   Sat May 23 16:15:38 2020 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi Frank,

Good bit of detective work. 
To me it suggests that something as yet undetermined
  
ELOG V3.1.5-3fb85fa6