By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?

I have added

port = 443

ssl = 1

Without sucess.

I then tried

port = 443

use_ssl = 1

still no sucess.

I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2)  reading all the documentation I cant seem to figure it out.

I also configured elogd to listen on port 443

Opened a CMD window and entered >elogd -p 443

Says listening on port 443 but still not working.

On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.

How do I make this section Wider or Shorter in the 2.7.8 version?
Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box. 

> How do I make this section Wider or Shorter in the 2.7.8 version?
> Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box. 

Never mind Found it

In Global set

Message Width = 95

Is there a way to enforce password complexity for users?

Either in this version of elog or the newest version?

Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?

I need to access 2 different elogd.cfg files.

 I need to do this because there are 2 different groups that each have 6 or 7 different logbooks in their elogd.cfg files.  (and they can't access each others log books)

Currently the first group  accesses elog as http:elog.com:8080.  The elogd windows service executes "C:\Program FilesELOG\elogd.exe" -D -c "C:\Program Files\ELOG\elogd.cfg"  

From what I can tell, whats needed is either some way to get the windows service to run a different config file or there needs to be a way of creating a second elog windows service that points to a different elogd.cfg file. Is there some way of doing this?

 I will check out the "Top Groups". But another question, the documentation says "Prior to ELOG version 2.4.1, one had to run two elogd servers in parallel, listening under different ports." ... how do you set this up?

Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.

You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX  The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer event number 100098, first displaying the message where all of the ID is displayed and secondly in "full" view of the elog front page. Here, the "ID" column contains a link with the string: elog:SequencerEvents/10009. Our problem is that we often use this string to paste into other elogs and generate a link to the sequencer event message. However, since the string uses too few digits, we end up with a link to the wrong message