Re: Fail to install in mac, posted by Alex on Fri Feb 13 20:36:59 2015
|
Thanks! now install works fine - but I cannot find how to open and start writing- I do
/usr/local/sbin/elogd |
Re: Fail to install in mac, posted by Stefan Ritt on Fri Feb 13 21:18:46 2015
|
Point your browser to http://localhost:8080 as written in the documentation
Alex
wrote:
Thanks! now install works fine - but I cannot find how to open and start |
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. |
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, |
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.
|
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
|
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 |
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 |