Since I'n not a programmer I's like to be very carefulls with bug  
reports, but after testing for a while, I belive this my be a bug or  
something else:  
  
I have 2 systems running ELOG 2.5.1:   
1. uSE Linux 8.2, KDE 3.2 = NO problems at all! ELOG work's in every  
function quiet well!  
2. The Internet Server (of my friend): Windows 2003 Server, All MS paches  
installed, Running IIS 6.0 Port 80) and ELOG 2.5.1 (Port 8080) under  
FireDeamon 1.6GA (actual release) as a Service (Deamon).   
  
Problem under Win 2k3:  
This works very well, even with several users on the system and on ELOG  
as long as there is not msg. threaded! Is a Msg. Treaded ELOG produces  
the msg. showen in the attached Jepg-file below on Win 2k3.  
The problem occurs as soon as Elog would change to the threaded display 
or by clicking "Repaly" in the menu. Rights etc. are aleady checked on 
the file system and are looking well. Everithing will work well as 
nothing is thraded or testing locally under Linunx. 
 
Does anybody  
have an idea??? It my by a bog on Elog as well as from Microsoft or a  
problem produced by a dummy user (me...!). Since Linux don't have the  
problem and the same cfg-file and log-files are working well if I don't  
use mode=threaded as well as Display mode = threaded I believe it my be a  
realchance not to be the personal factor of the dummy user...   
  
ThankX for every hint!  
  
  

Thank's!!!  :-)) 
 
Great solution. Exactly what I need! 
 
Ueli 
 
> This can be easily achieved with the configuration option 
>  
> Start page = ?sort=<attribute> 
>  
> or 
>  
> Start page = ?rsort=<attribute> 
>  
> where <attribute> is your date. 
>  
> In your case, you need the URL 
>  
> http://www.familienhund.ch:8080/Aktuelles+Programm/?sort=Datum+wann 
>  
> which can be obtained via 
>  
> Start page = ?sort=Datum+wann 
 
 

This can be easily achieved with the configuration option

Start page = ?sort=<attribute>

or

Start page = ?rsort=<attribute>

where <attribute> is your date.

In your case, you need the URL

http://www.familienhund.ch:8080/Aktuelles+Programm/?sort=Datum+wann

which can be obtained via

Start page = ?sort=Datum+wann

I really don't know if anybody already had this problem or i just didn't 
find the solution in the documenttaion: 
 
There is a possibility to sort the log by the value of a attribute as 
well as a flag for reverse sort. anf it's quite easy to build up a 
command line with the sort attribute and value. But this only works from 
a self written command line. 
 
Is there any possibilty to make ELOG soring by default (without a 
command line option) by a other attribute than date? I would use a date 
set by the user manually to sort the log file, even the user clicks on 
the log-name.  
 
or may it be a possibility for a additional feature, like a logbook 
option "Default sort = my own date" and the logbok get sorted by this 
attribute and option by default. 
 
Would be happy about every tip! ThankX! 

I have added that functionality according to your request. In elogd.cfg, you 
can specify

List Display = ID, Edit, Delete, Date, Author, ... <other attributes>

which gives you two colums, one to edit and entry and one to delete one. See 
the attached picture. I presume that's what you want. This works on the 
newest version 

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

and you need the two icons

http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/edit.gif?rev=1.1
http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/delete.gif?rev=1.1

to be put under your elog/themes/default/ directory. Or you wait for the 
next official release (;-)

How I can dynamically create a link when a new submission is entered that 
will have a value of <ELOG_URL$message id?=Edit>
I want the users to be able to go straight from the main page to an edit 
page. This would skip 1 step to get to the edit page.
Is this possible. 
If that link could use one of the icons for the src image that would be 
great. 
Thanks.
:-)

Noee. Here it works immediately.

Can you try with a fresh server from the distribution, with the example 
elogd.cfg, to see if there is any difference?

The killing is handled in the funciton ctrlc_handler(), which sets _abort = 
TRUE. This  is checked in line 16195, just after the select(), and the main 
loop is exited. The select finishes after one second, although I believe 
that the kill signal also terminates the select prematurely. The kill 
command and a Ctrl-C keystroke should work the same way, they both generate 
a SIGTERM or SIGINT signal.

When trying to stop elogd processes with the kill command
elogd exits only after access to the logbook.

It should exit immediately, maybe after some cleanup.