> Hi Stefan,
> 
> Must have missed it when the fixed/not fixed thread marking got implimented.
> 
> Anyhow, my main point would still apply for where the thread is not yet fixed, but is in one of a number of possible
> states  (waiting, panic, work-in-progress....).  Clearly you can label the latest entry in a thread with the latest
> status, and icon, but when in collapsed mode, you only see the initial entry.  If the latest entry were shown
> (optionally), then one can tell at a glance in the collapsed listings which entry may need direct attention.

If you always mark the whole thread with states (waiting, panic, work-in-progress,...) as described in my last posting, 
then you will see this from the thread initial entry as well. If you use icons, then even more. The only disadvantage 
is that you have to discipline yourself always modifying the whole thread and not only one entry in that thread.

Tried 2178 and I seem to hit some endless loop when I have big cookies. The loop seems to be in this for-loop (from gdb).

I perhaps you should have:

for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )

   if (i < (int) sizeof(cookie)-1)

      cookie[i++] = *p++;

   else
      break;

   cookie[i] = 0;

... Seems to be working for me =)

Yepp, you're right. I applied your change to the distribution code. 

Hello,

Please could you help me.

We have 2 elog servers synchronized every minute via Elog mirroring function.

2 or 3 times a week, the slave crashes and we have to restart Elogd. I have found in /var/log/messages the same message every time elogd crash :

xmalloc: not enough memory

Thanks.

Dominique Bolla.

I have a really odd issue with elog...

My setup:

elogd.cfg:
[global]
port = 2109
SMTP host = localhost
Resource dir = /usr/share/elog
Logbook dir = /srv/www/elog
charset = UTF-8
Main Tab = main
URL = https://elog.codemages.net
Relative redirection = 1
Usr = www
Grp = www
Resolve host names = 0
Self register = 0 
Admin user = ruskie
SSL = 0
Login expiration = 20

[links]
Subdir = links
Theme = default
Comment = Link spam
Attributes = Author, Category, Link, Comment
Options Category = General, Law, IT, Odds, Linux
Required Attributes = Link, Comment
Page Title = ELOG - Link spam
Reverse sort = 1
Quick filter = Date, Category
Time format = %Y-%m-%dT%H:%M
Date format = %Y-%m-%d
Password file = links.pwd
Admin user = ruskie
RSS Title = $logbook $entry time :$Author :$Link :$Comment

[notes]
Subdir = notes
Theme = default
Comment = Various notes
Attributes = Category, Comment
Options Category = General, Law, IT, Odds, Linux
Required Attributes = Comment
Page Title = ELOG - Various notes
Reverse sort = 1
Quick filter = Date, Category
Time format = %Y-%m-%dT%H:%M
Date format = %Y-%m-%d
Password file = notes.pwd
Admin user = ruskie
RSS Title = $logbook $entry time :$Comment


lighttpd.conf:
$HTTP["host"] =~ "elog.*" {
  proxy.server = ( "" =>
                   ( "10.0.0.10" =>
                     (
                       "host" => "10.0.0.10",
                       "port" => 2109
                     )
                   )
                 )

}

If I access elog directly on 2109 I get no issues but when I use this configuration it takes minutes to access
any elog page at all. But the odd thing is this only happens when I'm using a gecko based browser(firefox,
xulrunner based etc...) if I use webkit-gtk or elinks all the pages load up with no noticable delay.

I have tried this on different computers, different configurations and so on... And always the same behaviour
when it comes to a gecko based browser. Elinks and webkit-gtk load up fine.

Marking this as Other so far. If anyone knows anything about running elog and lighttpd togheter please speak up.

Hello Stefan and Elog fans,

Is there a way to find entries with the words program and error when then are not contiguous in the text?

Thanks,
--Mike

Dear Stefan,

First of all, I appreciate that you made such a nice program. I've used elog for more than 5 years and it was wonderful experince to me and my research work was very productive with this.

I have a suggestion to you to improve this while I was using elog. If users can add texts or comments for each attachment, it will be great.

I am not sure if someone was already suggested this or it is already in your wish list.

Thank you.

Dongwook Jang

Dear Dongwook,

no, this is not implemented and also was never requested. The way most people work is that images are included directly in the text, and the the text goes along with that.

So for example if I want to show you the ELOG logo, I put it here:  

If I want to add a comment for an attachment, I write it in the text and just refence the attachment with link. This way is more flexible that adding just a line of text to each attachment, since you can write several lines in the text, make a table etc. etc.