Many Thank's to Stefan for his work!!! He's doing a great job and is offering a better 
service than most comercial programs! Thank you very much Stefan!!! 
 
The new elogd.exe is now runniung 24h on my Windows 2003 Server without any problems. I made 
a little "stress" test too and there wasn't any problems at all. Also threaded view is 
working stable now. 
 
Is seems, that the new eleogd.exe uses a litle bit less of system rescources especially in 
theraded view mode. 
 
System specification for test: Pentium 4 2,4GHz, ASUS Motherboard, 480 MB RAM, SWAP File 1,1 
GB, Windows Server 2003 Enterprise Edition 5.2 including all paches until 15.3.04, IIS 6.0, 
Mercure Mail Server 4, McAffee Virus Scan & Firewall, ELOG 2.5.1 with new eleogd.exe runnig 
as service (system righs) with FireDaemon Lite 1.6GE. 
 
Please note that this problem has been occured under windows (reported for XP, 2000, 2003 
Server) only. Windows NT 4.0 is working well without the new eleodg.exe as well. 
 
 
> This problem has been fixed now, it was a programming bug. New version under 
>  
> http://midas.psi.ch/elog/download/windows/elogd.exe 
 
 

Version 2.5.0 of ELOG has been released yesterday. The main new feature is 
the automatic mirroring of logbooks between different elog servers. 

This is useful if one wants to synchronize logbooks between a desktop PC 
and a laptop, for example. During synchronization, new or modified entries 
on both sides are merged intelligently. Another application is if several 
companies or institutes want to keep a ELOG database locally, but have the 
databases synchronized periodically with each other. Periodic mirroring 
can be set up with a built in cron-like facility. 

Although the synchronization has been tested extensively, I still consider 
this part in beta state. Before using it, one should make a backup of 
existing logbooks. The flag "Mirror simulate" can be used to test the 
mirroring without actually overwriting or deleting anything. If problems 
arise with mirroring, they should be reported to the author.

Localization files have been updated, so if anybody volunteers to update 
or make a new translation, please contact the author.

I have created a javascript to be used as a browser link that allows a one
step cut and paste from a web browser into a elog logbook. 

The intended application is allow a user to do a text selection in a web
browser, then click on a bookmark that automagically pastes the selected
text, the current browser page url, and the current browser page title into
a pre-defined elog logbook.   I do some research where I would like to save
some text from a webpage, but also have a record of where the webpage came
from.  However, you should find that you can extend this script in a varity
of ways for your own application.  

The script is a simple one: it uses javascript in a saved bookmark to get
your selected text, title, and url, and then creates a new browser window
with a elog form, and print the document variables into the form, and then
submits the form to elog.   The key advantage to this approach is that you
can use the "post" command, rather than "get", to submit to the text section
of an elog logbook.  The only way I found now to submit to elog via a
bookmark is using the "get" command, and it doesn't allow entry of the
"text" field, only attribute fields.    

The second major advantage to using POST is that you can submit a much large
quanity of information ; However, some checking on this leads me to believe
that the limit is browser and server depended, so YMMV.  However, a great
discussion on the limits of browsers can be found here: 
http://www.squarefree.com/bookmarklets/browsers.html .

One of the major limits is that IE6.0 browsers have a maxium of 508 bytes
per bookmark - This book runs over 800 bytes, so I suspect tha IE6+ will not
allow it.  I tested the link with Mozilla and Firebird 0.7.

This script will need to edited for you to use with your elog logbook.
The script should be fairly self-explainitory, if you are used to html forms
and have some exposure to javascript.

You will need to modifiy the following fields:

1) in form action = http://<your_domain.com>/elog/<logbook>/?cmd=New
      change the link to point to your specific logbook to be used for entry.

2) the attribute fields need match up with the ones in your logbook.

     The ones listed in the template are Author, Email, Title, and URL.

     If you have fixed fields (like Author and Email), then you can
predefine these fields as shown.  

      I have the page title used as the entry for Title, and the page url is
 use as the URL attribute.

      Finally, I have the text selection used as the entry for the Text field.

      You can add additional fields by creating a new <input ...>  segment
in the script.  For those more clever than me, you can concatinate the
title, url and selection to paste into the Text area as well.  

3) once you have a edited version of the script (make sure you keep it as a
single line), you can then create a new bookmark in your browser, and then
paste the script into the properties->location field (for Mozilla/Firebird)
or the properites->url field (IE).  Give it a good name like "post to elog"

4) once saved, you can then go a web page, select some text, and then go to
your bookmarks and click on the bookmark.  It should then create a new
window in elog with a completed logbook entry.


some notes:

1) again, this may not work on IE6+ browsers due to M$ limitations.

2) You may have to be logged in already to elog for this work - I have not
tested the interaction using a password protected elog

3) You can only post to a single elog logbook - You'll need to have multiple
bookmarks for multiple logbooks.
   

I find this script very nice. Indeed JavaScript can be very powerful to do such 
things. I added some JavaScript support to the elogd server itself. If one opens 
the "New" page like

http://localhost/demo/?cmd=New&js=test.js

then the JavaScript "test.js" (which has to be present in 
themes/default/test.js) gets inserted into the page header and executed. This 
can be used to add custom form validation, which is more powerful than the built 
in checking if required attributes are present.

Then I tried to redo the bookmark script with the new method. A server-side 
script has of course more space than just a bookmark. I started with a bookmark 
like:

javascript:window.open("http://localhost/demo/?cmd=New&js=test.js");

which even works on IE6. The script "test.js" contains:

function a()
{
  var d=opener.document;
  alert("test.js");
  alert(d.location.href);
  alert(d.getSelection());
}

a();

While the first alert() works, the others fail. It seems like the "opener" 
method does not correctly dereference the right window. If anybody has some 
idea, please let me know.

The new version of elogd which supports the "js=" command can be found here:

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.235

Around line 2240 (in loc()) in elogd.c the following is written, 
which results in an infinite loop, since loc() recursively with
the same argument "Change %s".

   /* special case: "Change %s" */
   if (strstr(orig, "Change ")) {
      sprintf(result, loc("Change %s"), orig + 7);
      return result;
   }

For now I just commented these lines.

Somehow elog does not use the -s option (subdir) anymore,
resulting in a 'HTTP/1.1 404 Not Found' error.

For now I am using elog from version 2.3.9 together with elogd v2.5.0,
which seems to work OK.

Maybe consider using the options -W -Wall when compiling elogd.
There are several warning messages.

This problem has been fixed recently. The new code is

   /* special case: "Change %s" */
   if (strstr(orig, "Change ") && strcmp(orig, "Change %s") != 0) {
      sprintf(result, loc("Change %s"), orig + 7);
      return result;
   }

Alternatively you can get the updated version from CVS.

- Stefan