ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
85
|
Thu Jul 25 19:17:13 2002 |
| Mo | msheikh25@hotmail.com | Bug report | | | elogd.cfg cannot be saved |
Hello,
In the newest version of eLog, I was having trouble saving the
configurations once I change them through the web interface. I can change
them and save them fine if I do it in notepad; but that way you have to
restart the elogd server. I think this is a bug on the new version unless
I am doing something wrong. Also I was wondering if you were going to add
any of the wish list items on version 2.0.6 (Conditional attributes seems
to have the most votes and would be an extremely helpful feature!! :-).
Thank You.
Mo. |
84
|
Wed Jul 24 17:29:00 2002 |
| Christian Korschan | Christian.Korschan@CTBTO.ORG | Bug report | | | Re: Compiling elog 2.0.4 on Solaris |
> > 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);
$ |
83
|
Wed Jul 24 17:24:31 2002 |
| Christian Korschan | Christian.Korschan@CTBTO.ORG | Comment | | | Re: elog-2.0.5 core dumps under Solaris |
> 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 :-( |
82
|
Wed Jul 24 16:44:44 2002 |
| Christian Korschan | Christian.Korschan@CTBTO.ORG | Bug report | | | elog-2.0.5 core dumps under Solaris |
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 ? |
81
|
Tue Jul 23 15:59:55 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Improved display speed |
Version 2.0.5 of elog has been released today. Among various bugfixes, the
display speed for threaded lists has been improved significantly. Display
all messages of this forum and press the reload button to see the
difference. |
80
|
Tue Jul 23 09:21:38 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: inserting pictures into a post |
> does elog have a way of inserting pictures into a post other than
including
> them as an attachment? i can put a picture in using html text, but
this
> method only works if the picture is stored on the local server. anyone
> placing a post from a remote machine cannot include a picture off of
their
> machine.
> any help?
> thanks.
Right now it is not possible to easily include pictures into the message
body, but I put it on the wishlist. Of course you can always refer to
external pictures if you submit your text as HTML and put the proper tags
there like this one:

and you can even scale them like

but of course this requires to have that image stored somewhere else. I
will
probably add a feature like
att:name.gif
which will reference a picture from the attachment, and will be converted
to
the full picture name after submitting that message. |
79
|
Tue Jul 23 09:16:01 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: change the Email From address used when sending notifications |
> Is there a way to change the From address used when sending notifications
> from ELOG? I was hoping there might be another attribute that would go
> along with the smtp host section.
>
> Thanks,
> Eric
Yes there is an option
Use Email from = xxxx
see documentation. |
78
|
Tue Jul 23 09:12:14 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | | | Re: Port specification with -p fails (SOLVED, more or less) |
> > Anyone seen similar problems?
> Probably not if you read the config file, 'cause I didn't. Shame on me...
>
> But what this shows (Stefan: correct me if I'm wrong) is that if you set
> the port number in the [global] section of the config file, the command-line
> option '-p' is ignored. FYI...
>
> Joeri
I changed that behaviour, so from 2.0.5 on the command line port setting has
precedence over the configuration file (as it should be). |