Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 713 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
icon4.gif   Trouble to install ELOG V3.0.0-72a8401 in XP SP3, posted by Pedro Acosta on Mon Mar 23 17:02:03 2015 
Hi,

It´s not possible to install the last version V3.0.0-72a8401 over XP SP3, the previous version works well.  For Windows
Vista Home Basic SP2 work fine the last version. 
    icon2.gif   Re: Trouble to install ELOG V3.0.0-72a8401 in XP SP3, posted by Pedro Acosta on Tue Mar 24 19:08:34 2015 
Maybe, nobody uses XP SP3 but i get Win32 invalid aplication error.  Not work!




Pedro
Acosta wrote:



Hi,
icon5.gif   elogd lost entry database without restart during file system trouble, posted by Andreas Luedeke on Thu Apr 30 09:54:17 2015 
I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
    icon2.gif   Re: elogd lost entry database without restart during file system trouble, posted by Stefan Ritt on Thu Apr 30 13:01:29 2015 
First, I can only fix problems which are reproducible. Can we do another power outage at PSI again?

But seriously, I guess what happened is that elog sees an empty directory when the AFS server
icon8.gif   Problem with autosave functionality when combined with no 'edit' button, posted by Thomas Lindner on Tue May 5 07:33:50 2015 
We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality. 
Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages.  So we have (up to
now), had the following set of commands specified in elogd.ccfg
    icon2.gif   Re: Problem with autosave functionality when combined with no 'edit' button, posted by Andreas Luedeke on Tue May 5 11:01:36 2015 
Hi Thomas,

just my two cent: as a quick workaround (for now) you could restrict editing messages to a short time range, like 30 minutes. That would cover
most cases of draft messages.

Restrict edit time = 0.5

 

But I agree that
    icon2.gif   Re: Problem with autosave functionality when combined with no 'edit' button, posted by Stefan Ritt on Tue May 5 12:05:47 2015 
I changed the code such that editing of draft messages is always possible, even if the "edit" command is not allowed otherwise. Update is in
GIT. Please check if that works at ND280.




Thomas
    icon2.gif   Re: Problem with autosave functionality when combined with no 'edit' button, posted by Stefan Ritt on Tue May 5 12:09:53 2015 
Arghhhh! Guess how many people asked me for the autosave feature! I worked really hard on it (including an airplane flight to Japan!), not the next guy
comes "can we disable that feature?". 
ELOG V3.1.5-3fb85fa6