ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
345
|
Mon May 19 19:14:35 2003 |
| Fred Hooper | fhooper@sushisoft.com | Bug report | | | Possible Bug: 2.3.7 : Welcome Title = < img src=""> not working |
Just upgraded (using rpms) elogd from 2.3.5
I am running on RH 7.3
I noticed that my custom start page did not display the Welcome title icon.
It worked fine in prior elogs.
Here's the syntax of the config file:
Welcome Title = <img src="thumb.gif"><p><font size=4 color=white>Elog</font>
Resource dir = /usr/local/elog/
"thumb.gif" is located in /usr/local/elog, and is readable by all.
I also tried the full file name in src=
<img src="/usr/local/elog/thumb.gif"> - same result.
any hints? |
351
|
Thu May 22 21:36:54 2003 |
| Roberto Morelli | morelli@es.net | Bug report | | | bug in cfg file | Hello Folks,
Found an interesting problem with 2.3.7 under redhat 9.0 linux.
When you take the elogd.cfg file and the menu commands = <list> and guest
menu commands = <list>, the config menu for edit the elogd.cfg stops
working, yet if I change the URL manually, I can still get to the file and
the menus do not change. If I delete all menu commands, then all works
without errors, yet the menus do not match default.
Also, the self registration function equal to 3 does not always send email.
Cheers,
Roberto |
379
|
Mon Jun 30 00:11:09 2003 |
| Joseph Giaime | giaime@phys.lsu.edu | Bug report | Mac OSX | 2.3.8 | runtime error under Mac OS X 10.2 | I have been trying to build and run elog under Mac OS X 10.2.6, without sucess. I
understand that this is not one of the 'supported' platforms, but I hope that there is someone
here who might know the work-around to my problem.
I've tried building elog 2.2.5, 2.3.6, 2.3.7, and 2.3.8. I've tried using the compiler that comes
in the Mac OS X 10.2 box, as well as the gcc-based compiler supplied in Apple's Dec 2002
developer update (gcc 3.1), and the June '03 update as well (gcc 3.3).
elog builds without error in all cases I tried.
When I run it, it will correctly serve the demo notebook. However, when the user clicks on the
test message to display it in full, there is a seg fault.
I suspect that the trouble might be with something defined in time.h.
I've run it in gdb, and the result is appended to this message. This is for gcc 3.3 and elog
2.3.8.
I would greatly appreciate any hints or suggestions.
Cheers, Joe
---
[satsuma:~/Documents/elog_build/elog-2.3.8] jgiaime% gdb ./elogd
GNU gdb 5.3-20030128 (Apple version gdb-282) (Fri Jun 13 03:33:07 GMT 2003)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "powerpc-apple-darwin".
Reading symbols for shared libraries .. done
(gdb) run
Starting program: /Users/jgiaime/Documents/elog_build/elog-2.3.8/elogd
Reading symbols for shared libraries . done
Indexing logbook "demo" ... ok
Server listening on port 8080...
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x00005870 in el_retrieve (lbs=0x1, message_id=50, date=0xbfff2500 "demo",
attr_list=0x0, attrib=0x365620, n_attr=1, text=0xbfff2280 "1", textsize=0x1,
in_reply_to=0x0, reply_to=0x0, attachment=0x0, encoding=0x0, locked_by=0x0) at src/
elogd.c:2775
2775 {
(gdb) up
#1 0x0001d9b4 in interprete (lbook=0x1 <Address 0x1 out of bounds>, path=0xbfff2280
"1") at src/elogd.c:12279
12279 show_elog_message(lbs, dec_path, command);
(gdb) up
#2 0x0001db10 in decode_get (logbook=0xbffff340 "demo", string=0x3a300a "1") at src/
elogd.c:12325
12325 interprete(logbook, path);
(gdb) up
#3 0x00020080 in server_loop (tcp_port=836736, daemon=-1073732640) at src/
elogd.c:13398
13398 decode_get(logbook, p);
(gdb) up
#4 0x00021134 in main (argc=1, argv=0xbffff850) at src/elogd.c:13832
13832 server_loop(tcp_port, daemon);
(gdb) up
Initial frame selected; you cannot go up.
(gdb) |
380
|
Mon Jun 30 02:12:24 2003 |
| Sridhar Anandakrishnan | sak@essc.psu.edu | Bug fix | Mac OSX | 2.3.8 | Re: runtime error under Mac OS X 10.2 | Joe,
Run the command
`limit' (if you are running tcsh) and `ulimit -a' if you are running bash
(these are command line programs that will tell you the resources you are
allowed to use. Look at filesize, datasize, and stacksize - these need to be
8M or so)
You can increase these by typing, e.g.,
limit filesize unlimited
limit datasize unlimited
limit stacksize unlimited
(the equivalent command for bash are `ulimit -f unlimited', `ulimit -d
unlimited' and `ulimit -s unlimited', without the quotes)
which will increase the limits to the max imposed by the administrator.
If that doesn't increase your limits, you will have to contact the admin to
have them raised system wide.
If you are the administrator/sole user, you can set them to the max in the file:
/etc/rc.common.
I have included the following at the end of the file:
##
# Enable coredumps if requested.
##
if [ "${COREDUMPS:=-NO-}" = "-YES-" ]; then
ulimit -c unlimited
ulimit -d unlimited
ulimit -s unlimited
fi
and I have put this in /etc/hostconfig
COREDUMPS=-YES-
Hope this helps - if that doesn't fix it, sorry!
Sridhar
> I have been trying to build and run elog under Mac OS X 10.2.6, without
sucess. I
> understand that this is not one of the 'supported' platforms, but I hope
that there is someone
> here who might know the work-around to my problem.
>
> I've tried building elog 2.2.5, 2.3.6, 2.3.7, and 2.3.8. I've tried using
the compiler that comes
> in the Mac OS X 10.2 box, as well as the gcc-based compiler supplied in
Apple's Dec 2002
> developer update (gcc 3.1), and the June '03 update as well (gcc 3.3).
>
> elog builds without error in all cases I tried.
>
> When I run it, it will correctly serve the demo notebook. However, when the
user clicks on the
> test message to display it in full, there is a seg fault.
>
> I suspect that the trouble might be with something defined in time.h.
>
> I've run it in gdb, and the result is appended to this message. This is for
gcc 3.3 and elog
> 2.3.8.
>
>
> I would greatly appreciate any hints or suggestions.
>
> Cheers, Joe
>
> ---
>
> [satsuma:~/Documents/elog_build/elog-2.3.8] jgiaime% gdb ./elogd
> GNU gdb 5.3-20030128 (Apple version gdb-282) (Fri Jun 13 03:33:07 GMT 2003)
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "powerpc-apple-darwin".
> Reading symbols for shared libraries .. done
> (gdb) run
> Starting program: /Users/jgiaime/Documents/elog_build/elog-2.3.8/elogd
> Reading symbols for shared libraries . done
> Indexing logbook "demo" ... ok
> Server listening on port 8080...
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> 0x00005870 in el_retrieve (lbs=0x1, message_id=50, date=0xbfff2500 "demo",
> attr_list=0x0, attrib=0x365620, n_attr=1, text=0xbfff2280 "1", textsize=0x1,
> in_reply_to=0x0, reply_to=0x0, attachment=0x0, encoding=0x0, locked_by=0x0)
at src/
> elogd.c:2775
> 2775 {
> (gdb) up
> #1 0x0001d9b4 in interprete (lbook=0x1 <Address 0x1 out of bounds>,
path=0xbfff2280
> "1") at src/elogd.c:12279
> 12279 show_elog_message(lbs, dec_path, command);
> (gdb) up
> #2 0x0001db10 in decode_get (logbook=0xbffff340 "demo", string=0x3a300a
"1") at src/
> elogd.c:12325
> 12325 interprete(logbook, path);
> (gdb) up
> #3 0x00020080 in server_loop (tcp_port=836736, daemon=-1073732640) at src/
> elogd.c:13398
> 13398 decode_get(logbook, p);
> (gdb) up
> #4 0x00021134 in main (argc=1, argv=0xbffff850) at src/elogd.c:13832
> 13832 server_loop(tcp_port, daemon);
> (gdb) up
> Initial frame selected; you cannot go up.
> (gdb) |
419
|
Thu Jul 31 16:02:41 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.3.9 | not proper HTML |
I just upgraded from 2.3.5 to 2.3.9.
There are some errors in the generated HTML. Most of the time
the browser renders everything correctly but sometimes not. Please
check especially (http://validator.w3.org/):
- http://midas.psi.ch/elogdemo/Database/7
There are too many <table> tags before the attribute list:
'Type', 'Operating system',... This should be just one table and
not each row a separate table. Also the first <table> tag lies
outside a <td> tag of the enclosing table.
- http://midas.psi.ch/elogdemo/forum/ |
420
|
Fri Aug 1 13:18:42 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug fix | Linux | 2.3.9. | problem with boolean attributes | Boolean attributes were not displayed correctly in version 2.3.9.
Patch is attached. |
Attachment 1: elog.diff
|
--- elogd.c Fri Aug 1 13:13:09 2003
+++ elogd.c_ Fri Aug 1 13:12:59 2003
@@ -11275,10 +11275,10 @@
{
if (atoi(attrib[i]) == 1)
rsprintf("%s:</td><td class=\"%s\"><input type=checkbox checked disabled></td>\n",
- attr_list[i], class_value);
+ class_value, attr_list[i]);
else
rsprintf("%s:</td><td class=\"%s\"><input type=checkbox disabled></td>\n",
- attr_list[i], class_value);
+ class_value, attr_list[i]);
}
/* display image for icon */
else if (attr_flags[i] & AF_ICON)
|
421
|
Mon Aug 4 14:02:52 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug fix | Linux | 2.3.9. | width of the textarea is too large (after reply) | The width of the textarea after pressing reply is too large.
The problem is that the algorithm that searches for the longes line
looks for the next '\r' which it does not find and therefore takes the
number of characters in the text to be the width of the longest line.
To search for '\n' instead should solve the problem. Please find the
diff output below.
$ diff -c elogd.c elogd.c~
*** elogd.c Mon Aug 4 13:57:35 2003
--- elogd.c~ Fri Aug 1 13:13:09 2003
***************
*** 6028,6035 ****
p = text;
do
{
! /* pend = strchr(p, '\r'); */
! pend = strchr(p, '\n');
if (pend == NULL)
pend = p+strlen(p);
--- 6028,6034 ----
p = text;
do
{
! pend = strchr(p, '\r');
if (pend == NULL)
pend = p+strlen(p);
|
437
|
Sun Oct 12 08:37:00 2003 |
| Christopher Jones | cjjones@zombieworld.com | Bug report | Windows | 2.3.9 | Elogd.exe Crashes When There are too Many Replies to Replies... | Hi,
We have been using Elog successfully as a shiftlog book for over a month
now, but I recently ran into an annoying bug, I think.
We had a thread that was created and was being replied to over several
days. We first replied to the original thread and then each subsequent
reply was a reply of the previous reply. When the thread reached above 13
of these, the elogd.exe would crash everytime a user attempted to select
the logbook that contained the enormous thread.
I found the only workaround was to manually delete the offending entry
from the log file and to instruct my users to not reply to replies unless
absolutely necessary. I have been able to replicate this error across the
rest of my logbooks as well. If there is any more information you may
need, please feel free to contact me.
Thanks,
Chris Jones |
|