unless i missed these in the docs some place:

1) a threaded display but collapsed threads unstead of all replies showing

2) the subject is the link along with the icon. it would make it a little   easier to click on the message if you run your montior on a high resolution...

> unless i missed these in the docs some place:
> 
> 1) a threaded display but collapsed threads unstead of all replies showing

This feature has been added in Version 2.2.4 which has been released today. 
Use the "collase" button.
 
> 2) the subject is the link along with the icon. it would make it a little   
easier to click on the message if you run your montior on a high resolution...

This feature has been added in Version 2.2.4 as well. Use "line as link = 1" 
in elogd.cfg

> This feature has been added in Version 2.2.4 which has been released today. 
> Use the "collase" button.

> This feature has been added in Version 2.2.4 as well. Use "line as link = 1" 
> in elogd.cfg

thanks. that was quick :)

Starting from version 2.2.4 which has been released today, the 
option "quick filter" has been added. A "quick filter" is a drop down box 
on the message display page. By selecting a value from the drop down box, 
only messages of that type are displayed. See this forum which uses "Quick 
filter = Date, Category".

This new option adresses a couple of installations which require a large 
number of logbooks. Instead of using many similar logbooks, the old logbook 
name can now be defined as an attribute. All messages get now mixed, but by 
defining the logbook attribute as a quick filter, one can display the 
messages belonging to the individual logbooks separately with a single 
click.

In the "find" command, when searching over all logbooks, it
would be nice to see ALL attributes, which are common for all
logbooks (e.g. typically the author name), not just
logbook name, date and text.

> In the "find" command, when searching over all logbooks, it
> would be nice to see ALL attributes, which are common for all
> logbooks (e.g. typically the author name), not just
> logbook name, date and text.

That depends on how you specify what gets displayed in a search (with 
the "Display search" option for example). If you try the following link:

http://midas.psi.ch/elogdemo/Forum/?mode=summary&all=1

you see that all attributes are displayed from the three logbooks in this 
installation.

> > In the "find" command, when searching over all logbooks, it
> > would be nice to see ALL attributes, which are common for all
> > logbooks (e.g. typically the author name), not just
> > logbook name, date and text.
> 
> That depends on how you specify what gets displayed in a search (with 
> the "Display search" option for example). If you try the following link:
> 
> http://midas.psi.ch/elogdemo/Forum/?mode=summary&all=1
> 
> you see that all attributes are displayed from the three logbooks in this 
> installation.

How does the corresponding elogd.cfg entry look like for the
display search command ? - I can't reproduce this behaviour...

> > > In the "find" command, when searching over all logbooks, it
> > > would be nice to see ALL attributes, which are common for all
> > > logbooks (e.g. typically the author name), not just
> > > logbook name, date and text.
> > 
> > That depends on how you specify what gets displayed in a search (with 
> > the "Display search" option for example). If you try the following link:
> > 
> > http://midas.psi.ch/elogdemo/Forum/?mode=summary&all=1
> > 
> > you see that all attributes are displayed from the three logbooks in 
this 
> > installation.
> 
> How does the corresponding elogd.cfg entry look like for the
> display search command ? - I can't reproduce this behaviour...

Ok, finally I can confirm the problem. It will be fixed from Version 2.2.4 
on.

this is happened before, and it just happened upgrading from 2.2.2 to 2.2.3

the link at the bottom of the page shows a previously installed version.

i don't install to the elog directory, i install to a ram disk and copy over the new executables, the source, readme and help html.

the link showed 2.1.2 until i upgraded to 2.2.2 (i didn't do anything different than the above. now i'm at 2.2.3 and the link is showing 2.2.2...not that it's a big deal, i'm just wondering what i did wrong

> this is happened before, and it just happened upgrading from 2.2.2 to 2.2.3
> 
> the link at the bottom of the page shows a previously installed version.
> 
> i don't install to the elog directory, i install to a ram disk and copy 
over the new executables, the source, readme and help html.
> 
> the link showed 2.1.2 until i upgraded to 2.2.2 (i didn't do anything 
different than the above. now i'm at 2.2.3 and the link is showing 
2.2.2...not that it's a big deal, i'm just wondering what i did wrong

Of course you have to stop the old elogd program and start the new one. Have 
you done that?

> Of course you have to stop the old elogd program and start the new one. Have 
> you done that?

on windows i run it as a service through firedaemon, but i stop it before upgrading...that was one of the first things i checked...

> > Of course you have to stop the old elogd program and start the new one. 
Have 
> > you done that?
> 
> on windows i run it as a service through firedaemon, but i stop it before 
upgrading...that was one of the first things i checked...

Well, the other thing is that the previous page is till in the cache of 
Netscape. You have to hit "Reload" in order to properly update the page.

Besides these two things - browser cache and not stopping the old versoin - 
there is no possibility how you could see the old version at the bottom of 
the page, I update this very carefully on each distribution.

Ooops, I just realized that the Windows 2.2.3 distribution contained the old 
(2.2.2) executable for elogd.exe. I apologize for that. I have updated the 
elog223.exe distribution just now, so please download it again in order to 
get the new file.

- Stefan

> Ooops, I just realized that the Windows 2.2.3 distribution contained the old 
> (2.2.2) executable for elogd.exe. I apologize for that. I have updated the 

that's ok. i just it was driving me nuts there for a while...everything is fine now...

i've tried other web based msg boards, but i keep coming back to elog...

Typing in a text for a new entry results in an error message, whenever
one forgets to fill in mandatory attributes (as it should happen !). However
after using the back button in this case (Using netscape 4.79) I made the
experience, that the text typed in gets lost. Other browsers like Mozilla
or IE do not have this problem. Any idea how this problem can be
avoided for netscape as well ?

In my bottom.html file I have:

<A Href="host/Forum/?mode=summary&reverse=1&npp=10&Status=Open">Open</A> 
<A Href="host/Forum/?mode=threaded&reverse=1&npp=10&Status=
Open">(Threaded)</A> /                                                   
  <A Href="host/Forum/?mode=summary&reverse=1&npp=10&Status=C
losed">Closed</A> /  
<A Href="host/Forum/?mode=summary&reverse=1&npp=10">All</A>
<A Href="host/Forum/?mode=threaded&reverse=1&npp=10">(threaded)</A> 
tickets.

This sort of implements some of the buttons you have in your whishlist.

This works, because it is the same for all users, now what I would like 
is to add some sort of linke that will "show all entries from ME". I 
could do this on a per user basis, but that's not what I want, Something 
general with $user would be preferable.

Something like:

http://midas.psi.ch/elogdemo/Forum/?mode=threaded&reverse=1&npp=8&Author=$user

Is this possible ?

> In my bottom.html file I have:
> 
> <A Href="host/Forum/?mode=summary&reverse=1&npp=10&Status=Open">Open</A> 
> <A Href="host/Forum/?mode=threaded&reverse=1&npp=10&Status=
> Open">(Threaded)</A> /                                                   
>   <A Href="host/Forum/?mode=summary&reverse=1&npp=10&Status=C
> losed">Closed</A> /  
> <A Href="host/Forum/?mode=summary&reverse=1&npp=10">All</A>
> <A Href="host/Forum/?mode=threaded&reverse=1&npp=10">(threaded)</A> 
> tickets.
> 
> This sort of implements some of the buttons you have in your whishlist.
> 
> This works, because it is the same for all users, now what I would like 
> is to add some sort of linke that will "show all entries from ME". I 
> could do this on a per user basis, but that's not what I want, Something 
> general with $user would be preferable.
> 
> Something like:
> 
> http://midas.psi.ch/elogdemo/Forum/?
mode=threaded&reverse=1&npp=8&Author=$user
> 
> Is this possible ?

I added this feature in version 2.2.3, so now you can click on

http://midas.psi.ch/elogdemo/Forum/?mode=threaded&reverse=1&npp=8&Author=$long_name

and see all your entries.

Hello,
I am running Elog V2.1.3 on Solaris 8 and I was very pleased about this 
tool.But now I have a problem: Sometimes it takes a lot of time submitting 
an entry into a logbook, up to 3 minutes. This behaviour does only occur 
sometimes. Did anyone of You experience something like this?

> Hello,
> I am running Elog V2.1.3 on Solaris 8 and I was very pleased about this 
> tool.But now I have a problem: Sometimes it takes a lot of time submitting 
> an entry into a logbook, up to 3 minutes. This behaviour does only occur 
> sometimes. Did anyone of You experience something like this?

I have seen that behaviour only with certain versions of Netscape, running on 
the same machine than the elogd server. Since I did not observe this with IE 
or Opera, I attributed this to a Netscape flaw. Have you tried different 
versions of Mozilla?

- Stefan

We had the same problem here. What worked in our case was:

Traffic to port 113 (identd) was blocked. Because the server didn't give any
response at all there was a time-out to which we were waiting.  Opening up
the 113 port significantly speeded things up. Even when no ident-deamon was
running on the system. (it now gets an immediate no deamon running msg, and
can go on with it's processing instead of having to wait for a time-out)

On our:
   SunOS operator 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10

I get:

% make
gcc -g -O -o elog elog.c 
Undefined                       first referenced
 symbol                             in file
socket                              /var/tmp/ccgK4x1V.o
recv                                /var/tmp/ccgK4x1V.o
gethostbyname                       /var/tmp/ccgK4x1V.o
send                                /var/tmp/ccgK4x1V.o
gethostbyaddr                       /var/tmp/ccgK4x1V.o
connect                             /var/tmp/ccgK4x1V.o
ld: fatal: Symbol referencing errors. No output written to elog
collect2: ld returned 1 exit status
make: *** [elog] Error 1


I have no idea what is going on here

From: http://elog.sourceforge.net/

Solaris

It was reported by Martin Huber that under Solaris 7 following command must 
be used to compile elog:

gcc -L/usr/lib/ -ldl -lresolv -lm -ldl -lnsl -lsocket elogd.c -o elogd

It was also reported that the keep-alive mechanism is not working under some 
Solaris systems, so you need to start the elogd server with the "-k" flag to 
turn keep-alives off. 



Yep... does the job.
(even with 2.2.2 under Sol 8)