It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1

Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails.  I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing.  This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.

I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails.  I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing.  This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.

I would like to share my findings about the solution of our problem:

One of my collegues used elog in a way it was not intended for, he put an endry with 8021 lines of text.

So I grabbed the corresponding 160517a.log file from logdir, renamed it to a text file and created a new entry with the large textfile as attachment.

Since then, no more crash of elogs.

May this contribution be useful to other elog users...

Christian

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

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?

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 a