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.

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.

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!  
  
  

All I can offer is send me your config file for the problematic logbook, and 
I will try to reproduce the error.

hello stefan 
 
sorry for the delay, was out of the office today. i had tested the same config 
and logbook under a "pseudo" win nt installation (suse linux 8.2 with vmware 
4.01 (virtaual pc simualtion) and a nativ win nt 4.0 sp6a: there is no 
problem! as well as this configuration works under linux as daemon. 
 
the problem only ocures on win 2003 server. I d'dn't test it under xp, 2000, 
2002 beause i don't have any of this systems. but it looks that no one else 
has this problem. would be helpfull to know if there anybody out in 
cyberspase using elog 2.5.1 with win 2000 or 2002 or even better with win 
2003 server? or do you have a 2003 server at psi? 
for me it looks like a incompatibility of a stack, boffer overrun or somethin 
in the memory. for me it really only occurs under win 2003. thats what i'm 
wondering. the system memory test of the server was ok (no virus, non 
controller problem or something, else, checked the hole stuff agian, just to 
be really shure!) , other apps don't have any problmes (it isonly iis 6 and 
mercure mail server runnig on this system with about 20gb free disk and about 
500mb ram totally and a pentium 4). 
 
if you think you have a chance to reproduce the problem i can zip the config 
file and the log for you. but in my opinion, you will need a win 2k3.  
 
i'd chdcked the file system rights again to be shure that they are ok. also 
i'd checked that elog run as a system service under win 2k3. it should have 
all rights. changing to run eleog with administrator rights didn't change 
anything. 
 
would be great to find out what's happen. in the mean time i let it untreaded, 
hoping no one will click treaded view...  ;-)  for security, the servie is 
configured to restart if it hangs and to boot the system in an emergency, but 
it shouldn't happen evry hour... 
 
thakX! 
ueli 
 
 
 
> All I can offer is send me your config file for the problematic logbook, and  
> I will try to reproduce the error. 
 
 

> the problem only ocures on win 2003 server. I d'dn't test it under xp, 2000, 
> 2002 beause i don't have any of this systems. but it looks that no one else 
> has this problem. would be helpfull to know if there anybody out in 
> cyberspase using elog 2.5.1 with win 2000 or 2002 or even better with win 
> 2003 server? or do you have a 2003 server at psi? 
> for me it looks like a incompatibility of a stack, boffer overrun or somethin 
> in the memory.

I agree. It's most probably a stack overflow problem. The stack size must be less 
on a win 2003 server compared to a xp machine. I know that the threaded display 
requires some more stack space than the other displays. But unfortunately I have 
no win 2003 server here to try.

> I agree. It's most probably a stack overflow problem. The stack size must be 
less  
> on a win 2003 server compared to a xp machine. I know that the threaded display  
> requires some more stack space than the other displays. But unfortunately I have  
> no win 2003 server here to try. 
 
since the new server isn't standing here in my office i can not test if older elog 
versions don't have the problem too. but if your idea of stack or buffer overflow 
is right, i guess that hoping of the helpfull ms pach or a update of the compiler 
will be the only what we could do  :-(  it's always the same using software fom a 
company named "kleinstweich"...  ;-( 
 
is there a posibility in elog to switch off the threaded view or to say what kind 
of views are allowed? this would be helpfull in this case as well as it may be  a 
nice feature for other users too. elog is very powerfull, fo some users i think 
too powerfull with to many possibilities. i think about something like you made in 
the menu / guest menu option or maybe a flag to say "don't" make threaded dispaly 
possible", like e-mail formating or something else? 
 
 

BUG#1
Given:

Attributes = Category, Status, Started, Finished, Activity, Headline
Type Started = date
Type Finished = date
Options Status = 1-To Do{1}, 2-Opened{2}, 3-Closed{3}, 4-Suspended{4}
{2} Preset Started = $date
{3} Preset Finished = $date
{4} Preset Finished = $date

There seems to be no setting of Date format (or Time format?) that gives a
meaningful value to attributes Started or Finished.  Even "Date format = %s"
- which gives number of seconds since 1970 - gives bad results.

BUG#2
In single entry view, elog returns an unformatted date value for "Type =
date" attributes - even when it has been manually entered with the date picker.