I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook.
I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources) |
Hello,
Has anyone implemented an email gateway for ELOG, allowing users to submit entries by sending an email? Granted this should be possible using the elog client binary, but I thought I'd see if I've overlooked any examples or docs first.
Thanks!
Devin |
Is it possible to submit entries using the elog client binary when the server is configured with webserver authentication (when the server requires the X-Forwarded-User header)? One option would be if the server could support both webserver and kerberos (or even file) authentication, but neither
"Authentication = Webserver, Kerberos" nor "Authentication = Webserver, File" seem to work.
In addition to using the elog binary to talk to the elog server directly, we've unsuccessfully tried using curl to post data to the apache server url (URL in elogd.cfg). We can read entries using curl, but haven't yet been able to submit entries.
Any help would be greatly appreciated.
Many thanks,
Devin |
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there? |
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 |
Hello,
i have config file elogd.cfg like below:
[Tom Yaht]
Theme = default
;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook
;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2
Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to
Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager
;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated
The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading above.
Could anybody help me.
Thank you |