I'm not an expert in this field, but I think openssl is not meant to create a certificate for you, it is meant to create a certificate request form (CSR) and then you buy the certificate with that form from a vendor. Once you have the certificate then you just need to copy it to the right place for ELOG (or Apache) to use it, you don't need openssl for that.

You can have a look at: http://www.rackspace.com/knowledge_center/article/generate-a-csr-with-openssl

Good luck!

PS: This is of course an openssl question: another forum could may be more helpful?

I always chose the safe solution: I provide the full path to the document. For example (under Linux):

Preset text = /usr/local/elog/logbooks/inc/test.txt

Well, I only know that the following config file works fine for me on Linux:

[test]
Attributes = xx
Preset text = /tmp/xx

with the file /tmp/xx containing "test: ignore". When opening a new entry, then the text "test: ignore" is written in the editors text area.

I'm using Version 2.9.2

My suggestion: download the latest Windows Version and try again.

Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.

Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!

You are using the entry ID to sort your entries: there is no good way to insert a new entry ID, like 300.5

But you could sort your entries by other means, that allows you to insert entries later between existing entries.

I use for example a "when" attribute of type datetime. Here's an excerpt from the relevant part of my config file:

1a. If you go to the "Find" form, you can add filters on several attribute. The URL of the result page can be bookmarked: this is your filter.

1b. If you define quick filters on FROM and TO, then you can enter filters on both.

2. If you start elogd with the -x option, then you can execute scripts in the "subst" and "subst on edit" commands. Within those shell scripts you can use $START TIME and $STOP TIME to calculate the attributes value. Look for the "Subst" command in the documentation.

If you have the following elogd.cfg:

And the shell script /usr/local/elog/diff.sh is:

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

Then DURATION is calculated from START and END in full hours.

It appears that if you define START and END as "datetime", then only the date part would be passed to the script. This may is a bug of elogd: Stefan, have you ever tried?

PS: Please do NOT write all capital text in a forum. Thank you!