Most mail delivery systems have a maximum size for attachments. In the past, if an elog attachment was larger than this size, the email server refused to accept this email and no notification is sent. Now one can specify the maximum allowed email attachment size with

Max email attachment size = <n>

where <n> is the number of bytes. If an email attachment is larger than <n>, the attachment is not sent with the email notification, but rather replaced by a link to the elog server for that attachment. By clicking on the link in the email notification, a browser will then open and download the large attachment. For each each elog installation, the admin has to figure out what the maximum attachment size of their SMTP server is, and then put this number into the elogd.cfg setting  above. For most installations, the default of 10 MB will just work fine.

Stefan

Hello. We are using explicity subdir names on our elog server to manage a large number of "Top groups" and sub "groups". When we create a new logbook from a template in the same group, it would be beneficial to automatically give a new subdir based on the previous one. At the very least, it should not reuse the same parameter as the template (see below).

At the moment, it copies the subdir parameter from the template logbook, which results in the new logbook writing to the same location as the template. That is very confusing and has the potential to be harmful as people can (and recently did) decide to delete these "duplicate" entries. But they are not duplicates, they are the exact same entries as the template logbook and deleting them removes them forever!

The way around this at the moment is to manually update the subdir after copying, but then the logbooks need to be re-indexed before the new logbook will display correctly. That requires a manual restart of the elogd process, which is less than ideal. 

Starting from version 2.2.5 on, an new directory scheme has been 
implemented. The idea is to separate the config file from the theme/icon 
and the logbook directories. This can now be achieved by specifying the 
configuration file via the "-c" flag and the directories with the "-d" flag 
for the logbook root and the "resource directory" with the "-s" flag.

Alternatively, the resouce and logbook directories can be specified in the 
configuration file with

Resource dir = ...
Logbook dir = ...

The old "Data dir" statement is still possible but deprecated. Instead, the 
statement "Subdir = ..." should be used which is taken relative to 
the "Logbook dir". If no "Subdir" is given, the logbook name itself is used 
as the subdir. For this demo logbook I use now:

[global]
...
Resource dir = /usr/local/elogdemo
Logbook dir = /usr/local/elogdemo/logbooks

and no "Data dir" statements any more. The logbooks "Linux", "Database" 
and "Forum" are then located at

/usr/local/elogdemo/logbooks/Linux
/usr/local/elogdemo/logbooks/Database
/usr/local/elogdemo/logbooks/Forum

respectively. The help, theme and icon files are located at their old 
position ("themes" is automatically added to the "resource dir" as it was 
before).

Hi,

is it possible to create a new column on the main page? Between "Logbuch" and "Einträge" I need the new column for enter the IP from the servers.

Thanks for your help

Markus

Hi,

I added many features to ELOG recently, but before making a new release, I 
would like some beta testing. In addition to the current modes of 
operation, a logbook can be configured to require a user to be logged in to 
submit new messages. If not logged it, one can only read messages. To 
obtain a new account, one can do a self-registering. In this process, one 
can also enter the email address which is then filled in automatically on 
new logbook entries.

So please go to the forum logbook, create a new account for yourself and 
try things out. If there is any problem, please let me know.

Many thanks in advance, Stefan Ritt.

I noticed the site has been updated as far as the documentation for 2.3.1, 
however the latest version in the downloads section is 2.3.0, any other 
places where I can get 2.3.1

Cheers