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

A new version 3.1.2 of elog has been released today and can be retrieved through the normal download section. Since it fixes some vulnerabilities, it is recommended to update to this version.

Stefan

Hello,

I've been successfully using elog as a daemon since several years on a Linux machine. For some reasons recently I had to switch to a Windows 7 machine. Here, setting up the elog daemon doesn't work for me:

(a) running the command:

"...\ELOG\elog.exe" -c "...\ELOG\elogd.cfg"

in a windows shell works perfectly fine - logbook is up and running as set up in the cfg-file.

(b) However, starting the windows service manually (start->control panel->system and security->administrative tools->services) that was set up automatically during installation of elog leads to an error message:

"Error 1053: The service did not respond to the start or control request in a timely fashion"

From the service settings I can verify that the service is running exactly the same command that works in (a).

Could someone please share the windows service settings? Thanks in advance.

Cheers, Christian

These problems are usaully related to user rights. Try starting the service under a different (maybe admin) user.

Stefan

Hi Stefan,

you were right - running the service by an authorized user solved the problem.

Thanks a lot.

Cheers, Christian

hi

I have an elogsystem for documenting emergency services. I have a starttime and an endtime. Is it possible to calculate the diff between the 2 timestamps and convert it to minutes?

Attributes = Bereitschafts Kalender Woche, Bereitschafts Woche, Einsatzbeginn, Einsatzende, Einsatzzeit, Telefon Nummer, Station, Status, Problem 
Options Status= Offen{1}, Erledigt{2}, Geschlossen{3}

......

Type Einsatzbeginn = datetime
Type Einsatzende = datetime

....

Subst Einsatzzeit  = $shell(Einsatzende - Einsatzbeginn) 

regards

/alex

I found the solution in the forum :-)

subst Einsatzzeit = $shell(/usr/local/elog/diff.sh \"$Einsatzbeginn\" \"$Einsatzende\")

and diff.sh is

#!/bin/sh
#set -x
s1=$(date -d "$1" +%s)
s2=$(date -d "$2" +%s)
d=$(echo "($s2-$s1)/60"|bc -lq)
printf "%.0f Minuten" $d
 

is ist possible that subst only works for the initial create of a logbook entry? when I change/edit one of the parameter "Einsatzbegin" or "Einsatzende" the "Einsatzzeit" is not changed.

regards

/alex