The limit is in the variable 

#define MAX_N_ATTR      100

in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.

Stefan

I am modifying the elogd.cfg automatically with a script.  The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.

Everything worked fine, until we hit the critical number of 100 attributes.  I saw this is also stated in the manual.

Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior. 

Is there a reason for this limit?

Thanks

Jonathan

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 John,

I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.

Cheers,
Stefan 

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.

The setting

Use Email Heading

is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use

Email encoding = 1

and you get it.

/Stefan