Comiling elogd 2.0.4 under Solaris obviously fails with

gcc  -o elog elog.c -lsocket -lnsl
gcc  -o elogd elogd.c -lsocket -lnsl
elogd.c: In function `ss_file_find':
elogd.c:1372: `alphasort' undeclared (first use in this function)
elogd.c:1372: (Each undeclared identifier is reported only once
elogd.c:1372: for each function it appears in.)
make: *** [elogd] Error 1

because alphasort is an ucb'ism which does not exist under SYSV

... not very portable :-(

   If you have only one entry in the logbook and have it set up in threaded 
mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
of the entry or the number of the entry to see it, it does not allow you 
to.  If there is more than one entry, it works fine.  
   Also I wanted to make a submit page from where you could either go back 
to the logbook which you just entered a message for or type a new entry for 
that logbook.  First of all, is there a way to have only one file called 
submitpage.html in which I can define this for all logbooks or do i need it 
for ever logbook.  And also, is there a way I can even set a link that will 
allow to create a new entry.  I tried: 
    <a href="demo/?cmd=new">Enter</a> another message<p>

but for some reason it does not work.  Is there a way to implement this?

Thanks,
Mo

Hello,
    If you delete a message from the middle of a logbook that contains a 
bunch of messages, the message numbers do not get updated properly.  For 
instance, if you have 20 messages in the logbook, and delete number 15, 
entry numbers 16 through 20 all do not get subtracted by one; their numbers 
stay the same with #15 just missing in the middle.  

Mo

The last x link TEXT now shows up like this

   'Last 20 entries?mode=threaded'

I can not reproduce this with the elogdemo logbook, however.

This is not a serious bug...but when the global settings are as follows

[global]
Display mode = threaded
Reverse sort = 1

all logbooks with only a single entry produce the wrong URL on 
clicking "last 10"

The URL produced is http://localhost:8080/LogbookName/0
instead of http://localhost:8080/LogbookName/1

Ravi

Hello,

I noticed a strange behaviour with Elog 2.0.4 (i386 RPM) in Linux (RH 7.2). 
I started Elog out-of-the-box with portnumber 888 ('sbin/elogd -p 888').

It runs just fine, but appears to listen to port 8080, the default! It 
looks like the -p option on the command-line is ignored.

Anyone seen similar problems? 

Joeri

> 
> 
> This is not a serious bug...but when the global settings are as follows
> 
> [global]
> Display mode = threaded
> Reverse sort = 1
> 
> all logbooks with only a single entry produce the wrong URL on 
> clicking "last 10"
> 
> The URL produced is http://localhost:8080/LogbookName/0
> instead of http://localhost:8080/LogbookName/1
> 
> Ravi

This question has been answered in elog:55 .

Just compiled elog-2.0.5 under Solaris 8 and 9  without any warnings/errors
but the elogd binary just core dumps:

# /opt/ELOG/bin/elogd -c /opt/ELOG/elogd.cfg 
Indexing logbook "demo"...
Bus Error (core dumped)

.. tracing elogd shows:

[ lines snipped ]
2964:   brk(0x005B8A68)                                 = 0
2964:   ioctl(1, TCGETA, 0xFFBEE6BC)                    = 0
Indexing logbook "demo"...
2964:   write(1, " I n d e x i n g   l o g".., 27)      = 27
2964:       Incurred fault #5, FLTACCESS  %pc = 0x000164C0
2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
2964:       Received signal #10, SIGBUS [default]
2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
2964:           *** process killed ***
#

... any glue ?