You can change that yourself. Just find following line in elogd.c:

#define MAX_N_LIST      100

Ok, I finally found some time (I'm pretty busy these days) to add a check for a potential full file system in SVN revision 2258. So before the password file would get corrupted, elog shows an error message about the full file system and just stops to work until space is freed up. 

The solution is to use "Subst" instead of "Preset".

Hi,

I am using the # character to generate automatically incrementing numbers for new messages.

My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".

So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.

Maybe someone has a solution to this ?

Soren Poulsen

Hi

I'm doing something wrong but can't work out what! 

I've created a new logbook with some date attributes that need to keep in step, e.g. one date ("receipt date") is set to the date the new record is created and another ("response required") to 7 days later.  The logbook doesn't use threaded messages, just a single page for each log entry with Submin/Preview/Back.  The dates are set with:

Preset Receipt Date = $date

Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')

"receipt date" and "response required"  are set correctly when the log is written but if I change "receipt date" then "response required" is not altered - presumably because Preset only works on "New".  Tho I haven't found a way to make this dynamic with Subst.

When the log is updated later a third date may be entered ("proposal submitted") and this should calculate a fourth date ("proposal expires").  Again, I thought I could do this with some sort of "Subst" but can't work out how.  If I use Subst then the value of "proposal expires" isn't changed at all and if I use Subst On Edit then the value isn't changed until I go in to edit the log when the correct "proposal expires" date gets calculated and displayed, e.g.:

Subst On Edit Proposal Expires = $shell(gawk 'BEGIN{ if ($Proposal Sumbitted > 0) {print $Proposal Submitted + 86400 * 30}}')

Am I trying to do the impossible, and is there a document that will help me to understand when different updates (Preset, Subst, Subst On..., Change etc) happen and comparing their use?

A great piece of software - though I sometimes find it hard to get my head round all that it can be bent to do!

regards

Steve

> Like many educational institutions we get "educational certificates" that are chain certificates..
>  
> only shows: 
> 
> CONNECTED(00000003)
> 25523:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:562:
> 
> What do I do wrong?
> 

After reading the OpenSSL Documentation:

The certificates must be in PEM format and must be sorted starting with the subject's certificate (actual client or
server certificate), followed by intermediate CA certificates if applicable, and ending at the highest level (root) CA.

The chain.crt has to be of the following format:

HOST CERTIFICATE
INTERMEDIATE CERTIFICATE
ROOT CERTIFICATE

Then it is working w/o problems

GS

* Withdrawn *

The HTML layout produced by elogd is horrendous to deal with programmatically; I give up.

Hi,

I'm writing a greasemonkey script to slightly alter the look of the pages served by the ELOG server.  One difficulty that I'm struggling with is how to identify what type of page ELOG has created.  While I have several methods to determine the page type, such as a log entry vs. log entries summary, the solutions are not straight forward and not clean.  As far as I tell, there's no specific identification in HTML document currently that describes and identifies the type of page being served by the ELOG server.

So, I'm requesting that the pages created by ELOG be identified in some fashion with the META element, such as:

    <meta name="description" content="elog log entry" />

or

    <meta name="description" content="elog log summary" />

or even using the keywords attribute:

    <meta name="keywords" content="elog log summary" />

Thanks!

Hi,

Here is what happens (I think) if E-log encounters a full file system where it keeps the user authorization file:

1. When a user connects, E-log will make a backup of the file. The backup will be corrupt since the file system is full.

2. E-log will modify the contents of the original file, and write it back. The file will be corrupt since the file system is full.

3. Now, both the backup and the normal file are corrupt and you cannot log on, until someone cleans up the file system and restores a valid copy of the file.

Would it be possible to fix this ? Like abort if step 1 is not successful. And restore the backup file if step 2 is not successful.

Thanks a lot for you help 

Soren