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 ?

> 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 ?

Hmmm - stupid me used a broken patch  used to get rid of alphasort under 2.0.4
this entry and it's predecessor should be DELETED - sorry for the confusion :-(

> > 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 :-(
> 
> I was not aware of this. Actually, I don't need 'alphasort' so I removed it 
> from the source. The update is at
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> 
> Please give it a try.

ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
(scandir) that does not work under SYSV:

$ make
gcc -g -o elogd elogd.c -lsocket -lnsl
Undefined                       first referenced
 symbol                             in file
scandir                             /tmp/ccy0Z3iV.o
ld: fatal: Symbol referencing errors. No output written to elogd
collect2: ld returned 1 exit status
make: *** [elogd] Error 1
$ egrep scandir elogd.c
  n = scandir(path, &namelist, NULL, NULL);
$ 

using:
Display mode = threaded
List display = Subject, Type, Author, Date

in the config file (omitting "ID" then) rise the bug

ie, an unneeded "," is displayed after the "supposed to be printed" ID

A new version 3.1.5 of elog has been released with all accumulated fixes over the past actually few years. I made a tar file, a RPM, but I could not compile yet a windows version.

https://elog.psi.ch/elog/download.html

Best,
Stefan

Hi all,

ELOG V3.0.0-21dc563

Our elogd dies alwways when searching for full text:

elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.

The only change we did was adding/editing entries.

Does anyone else encounter the same issue ?

I did not find any hint in release notes that this issue would be fixed in a later version

Please don't get me wrong, I am not complaining. Elog does a great job for us since years.

Christian

It depends on how you actually call the elog client, but it outputs a message

 Message successfully transmitted, ID=(new message id)

to the console upon successful transmission. Maybe you can catch this and evaluate?