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)

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.

> Was wondering if there were any tweaks/suggestions for improving the 
> logbooks responsiviness.  Our logbook was started 31 July 01.  Since that 
> time we have went from 1 logbook to 4 logbooks.  Logbook 1 having 2651 
> entries, logbook 2 having 300 entries, and the last 2 are new logbooks, so 
> only a few entries.
> 
> When user launches the logbook website, it takes considerable time to bring 
> the site up.  It seems to be directly related to the number of entries in 
> the logbook.  If I set up a dummy site with a couple logbooks and only a 
> few entries, the logbook is very fast coming up as well as saving entries.
> 
> Another thing that seems to slow the site down, is the number of users in 
> the elog notification list (those who've subscribed).  When you save a log 
> entry, it takes around 30sec or longer for it to actually complete the 
> save.  If I remove the list of users from the notification list and just 
> have a few, the save is very fast.
> 
> 
> Thanks in advance,
> 
> Eric

2600 entries is too much for this application as it load the all files 
in computer memory
expand the server memory
Are you running on linux or Windows ? I suggest linux (faster)
We are working on the C source to move all data from flat to database like 
SQL or mysql
when a parameter flag like 'status' = "OK" for instance
I suggest also to split in several logbook
but this is depend on your 'ELOG' parametrisation and logics

If your data are not 'sensitive' I can check on my linux server

Etienne

> may be add a parameter
> 
> Restrict Search all logboog = 1 or 0
> if 1 the switch will not appear 

The flag "Search all logbooks" is already there! (I forgot about it!). So 
just set it to "0" and you should be fine.

- Stefan

Starting from version 2.2.5 on, an new directory scheme has been 
implemented. The idea is to separate the config file from the theme/icon 
and the logbook directories. This can now be achieved by specifying the 
configuration file via the "-c" flag and the directories with the "-d" flag 
for the logbook root and the "resource directory" with the "-s" flag.

Alternatively, the resouce and logbook directories can be specified in the 
configuration file with

Resource dir = ...
Logbook dir = ...

The old "Data dir" statement is still possible but deprecated. Instead, the 
statement "Subdir = ..." should be used which is taken relative to 
the "Logbook dir". If no "Subdir" is given, the logbook name itself is used 
as the subdir. For this demo logbook I use now:

[global]
...
Resource dir = /usr/local/elogdemo
Logbook dir = /usr/local/elogdemo/logbooks

and no "Data dir" statements any more. The logbooks "Linux", "Database" 
and "Forum" are then located at

/usr/local/elogdemo/logbooks/Linux
/usr/local/elogdemo/logbooks/Database
/usr/local/elogdemo/logbooks/Forum

respectively. The help, theme and icon files are located at their old 
position ("themes" is automatically added to the "resource dir" as it was 
before).

From Version 2.2.5 on, the configuration file entries

User = ...
Group = ...

have been changed to

Usr = ...
Grp = ...

in order not to conflict with the new "Group = ..." option which is used by 
hierarchical logbooks.

propose to put 
[Submit] [Back] [Submit & Notify] button on top/bottom

new parameter 'shell option' 

[test]
...
Attributes = NotifyMode, Param1....Param10, Adresse, Subject, ...
Options NotifyMode = mail, SMS, Fax, printer...

; this command will invoque a shell command  
; example       
ShellCommand = <my shell command> parameters ...

like in WINDOWS 2000
ShellCommand = START.EXE notify.bat $NotifyMode $Param1, $Param2, $Param3
; in this case no necessity to modify the C source
; in windows I suggest the start.exe with a exit command
; so no necessary to wait the return code from the shell

Can you consider implementing the following additions to the functionality

1) Subt on edit <attribute> = xyz 

This would be fantastic for implementing version control so you can see who 
has edited a posted or a db entry.

2) Have a SORT fieldname flag so you can decide which column to sort things 
by on a display listing in conjunction to the display flags, it current 
defaults to the # column and I find i am directly linking to a sorted 
display

3) Have the elogd.conf track actual log entries people have changed 
detailing date and time etc.

4) Ability to export contents of the log books to files on disk for backup 
purposes as all data is contained within a single log file which causes 
problem for command line searches.


Many thanks