<VirtualHost xxx.xxx.xx.xx>
    ServerAdmin our.email.address
    DocumentRoot /www/apache/htdocs
    ServerName our.server.name

    # Rules to new  elog 2.6.0 
    Redirect / https://our.server.name:9898

    ErrorLog logs/error_log
    CustomLog logs/access_log common
</VirtualHost>

<VirtualHost xxx.xxx.xx.xx:9898>
   # Here be standard configuration for the Virtual Host
   ServerName our.server.name:9898
   ServerAdmin our.email.address
   RequestHeader set Front-End-Https "On"

   # This be the path to the elog directory
   # (This didn't seem to make any difference, but it be a good
   #  idea nonetheless)
   DocumentRoot "/www/src/elog-2.6.0"

   # Here be the setup for the SSL component of the Virtual Host
   SSLEngine On
   SSLCertificateFile /www/apache/conf/ssl.crt/server.crt
   #SSLCertificateKeyFile /www/apache/conf/ssl.key/server.pem
   SSLCertificateKeyFile /www/apache/conf/ssl.key/server.key

   # Here be the setup options for the Proxy module
   ProxyRequests Off
   ProxyPreserveHost On

   # This be the root of the new Virtual Host, and it should be
   # redirected to the port the elogd server is listening to
   # (8082 on our poop deck).

   <Location />
        ProxyPass  http://our.server.name:8082/
        ProxyPassReverse  http://our.server.name:8082/
        SSLRequireSSL
   </Location>

   ErrorLog /www/apache/logs/error_log
   TransferLog /www/apache/logs/access_log
</VirtualHost>

URL = https://our.server.name:9898

URL = https://antares.ccuec.unicamp.br:9696

[IMG]elog:1/1[/IMG]

[IMG]elog:1/1[/IMG]

{"8o", "<img src=\"%sicons/eek.png\">"}

Our Unix server died, so we decided to move our old eLog to the new server, running Mac OSX. Elog version is earlier then 2013, I can not say

I read that on OSX  eLog must be intalled through "make" command

if I need to install eLog first, how to add all old information later?

I found a way to get this to work.  Define a "Messages" logbook for the messages to be broadcast.  None of the user installations need access to it. Use "Execute new = " to execute a script calling the elog command line client passing the message on to each target logbook.  Example:

--- elogd.cfg snippet begin ---

[Messages]

...

Execute new = mass_post.sh $text &

--- elogd.cfg snippet end ---

--- mass_post.sh begin ---

#!/bin/sh

elog -a Sender="System Administrator" -l "Logbook 1" $@

elog -a Sender="System Administrator" -l "Logbook 2" $@

elog -a Sender="System Administrator" -l "Logbook 3" $@

--- mass_post.sh end ---

The $@ expands to all the command line arguments, so the $text field, with all its spaces, gets passed correctly.  Sorry I showed you the example in bash/linux rather than in Windows, but I don't know Windows real well - you're better off translating into it yourself than my untested attempts.  The one thing I can tell you is that the "Execute new" command must include the "background fork".  In Linux this is provided by the & at the end of the line. In windows you'll need to use

Execute new = start "dummy" /min mass_post.bat

to background the process.  This is ESSENTIAL.  Without backgrounding the batch file, the elogd server will go into an infinite loop.  The parent process will wait for the child process to exit before continuing.  elogd is single-threaded, so the child process cannot start until the parent process has completed its current task (which is waiting for the child process to exit). 

You may need to tweak the above a little if you want to pass variable attributes to the script instead of defining them all in the script itself.