I have done all that you suggested and all I get is the Message ID # that takes 
me to the message.
I even upgraded to the 2.5.1 version. Then I placed the elogd.c in the SRC 
folder. Also placed the images in the themes folder.
When I edit the List Display line it throws all my columns off by 1.
No luck so far. 
Any suggestions?

PS
Thanks for such a quick reply!


> 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 (;-)

Hello,

I have a quick question regarding how to display text using the "Top text" 
feature in the elogd.cfg file.  I've made an entry that looks like the 
following:

Top text = <h1>TEXT TO DISPLAY</h1>

But instead of getting just "TEXT TO DISPLAY" I get something like this:

----begin page ---
/usr/local/elog         "TEXT TO DISPLAY"

...rest of page 

----end page ---

...that is, on the far left at the top of the page in unformatted text 
is "/usr/local/elog/" prepended to the text I want do display. 

I don't know if this is a bug, or (more likely) something misconfigured in 
my setup. But any help that could be provided would be most greatful.

Thanks,

Val   

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. 
 
 

Is there any possibility to start elogd as a service under NT/2000/XP 
having local service as its user? Yes, I've read the documentation. Maybe 
things have changed.
/Torsten/

I searched and found some problems people were having compiling it on Solaris.
However I didn't see anything else.

If your using it, was it hard to get it installed and working?

Have a working copy of 1.35 running on NT4 server.
Went to upgrade to latest version.
Stopped service, installed the 2.52 version, restarted service and when 
trying to connect get nothing but server not found, dns errors, etc.
Copy back the 1.35 elogd.exe and everything is fine - I can connect and add 
entries to log.
Copy 2.52 elogd.exe and nothing.

So being the bright boy, I unistalled E-log, went through the registry and 
yanked everything out that referenced ELOGD, rebooted, installed 2.52, made 
the necessary registry changes, started service and nothing. 

Stopped service and copied 1.35 Elogd.exe back into folder, started service, 
and everything works.

Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping 
back to 2.10 version before giving up.

This is a server that is patched to latest and runs quite well with 1.35.

tuens out that the first log file was causing the problem. Elconv would just hang 
on trying to convert it. renamed it, reran elconv, reload service and 2.51 elogd 
and all was working as it should.


> Have a working copy of 1.35 running on NT4 server.
> Went to upgrade to latest version.
> Stopped service, installed the 2.52 version, restarted service and when 
> trying to connect get nothing but server not found, dns errors, etc.
> Copy back the 1.35 elogd.exe and everything is fine - I can connect and add 
> entries to log.
> Copy 2.52 elogd.exe and nothing.
> 
> So being the bright boy, I unistalled E-log, went through the registry and 
> yanked everything out that referenced ELOGD, rebooted, installed 2.52, made 
> the necessary registry changes, started service and nothing. 
> 
> Stopped service and copied 1.35 Elogd.exe back into folder, started service, 
> and everything works.
> 
> Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping 
> back to 2.10 version before giving up.
> 
> This is a server that is patched to latest and runs quite well with 1.35.

Hello,

is it possible to have an guest account together with a global password file?

I tried to put the password file statement into the global section of
elogd.cfg. But in this case every user must login and it is not possible to
have a read only guest account. 
But if I put the password file statemnet into the logbook sections, it is
possible to access the logbooks in read-only mode without logging in. The
drawback of this solution is, that you have to login into every logbook
seperately.

Bertram