boundary problem with Type lists display, posted by Emiliano Gabrielli on Wed Feb 23 18:07:24 2005
|
using:
Display mode = threaded
List display = Subject, Type, Author, Date
in the config file (omitting "ID" then) rise the bug
ie, an unneeded "," is displayed after the "supposed to be printed" ID |
|
New elog version 3.1.5, posted by Stefan Ritt on Fri Feb 3 16:54:57 2023
|
A new version 3.1.5 of elog has been released with all accumulated fixes over the past actually few years. I made a tar file, a RPM, but I could not compile yet a windows version.
https://elog.psi.ch/elog/download.html
Best,
Stefan |
elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:16:31 2016
|
Hi all,
ELOG V3.0.0-21dc563
Our elogd dies alwways when searching for full text:
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
The only change we did was adding/editing entries.
Does anyone else encounter the same issue ?
I did not find any hint in release notes that this issue would be fixed in a later version
Please don't get me wrong, I am not complaining. Elog does a great job for us since years.
Christian |
Re: problems with https in Chrome and IE, posted by Yoshio Imai on Wed Jan 25 15:40:17 2012
|
| Might this be related to the problem reported by Allen? |
|
Re: Return Code, posted by Yoshio Imai on Mon Jan 30 18:23:39 2012
|
It depends on how you actually call the elog client, but it outputs a message
Message successfully transmitted, ID=(new message id)
to the console upon successful transmission. Maybe you can catch this and evaluate? |
|
Re: HW Requirements to run elog / Performance issues running on ARM, posted by Yoshio Imai on Thu May 10 15:34:39 2012
|
Hi!
Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.
Yoshio |
|
Re: Dual Time display and entry times, posted by Yoshio Imai on Mon Jan 14 13:33:19 2013
|
Depending on whether I understand your requirement correctly, the following solution should work:
- define an additional logbook attribute, say "UTC Date"
- preset it on entry creation and submission with the UTC timestamp (cf. section "Attributes" of the ELog configuration guide):
Preset UTC Date = $utcdate
Subst UTC Date = $utcdate - prevent the attribute from being changed manually by adding it to the
Locked Attributes = < ... > andFixed Attributes Edit = < ... > lists, respectively.
You may also have to add it to theRemove on reply = < ... > list if replies turn out to keep the "UTC Date" value of the original entry.
Regards, |
|
Re: 5.5.4 cannot decode AUTH parameter, posted by Yoshio Imai on Sat Nov 22 16:05:34 2014
|
| harish amin wrote: | Dear Stefen,
Please help me & reply on my request. Is my global config correct? |
I am afraid you misunderstood Stefan. The lines he suggested to you are not something to put into your config file, but something you have to type on the command prompt in order to communicate directly with the mail server (i.e. completely independent from elog). You may have to ensure that the necessary communication program is installed on your computer.
Regards
Yoshio |