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

Has just been fixed. Available under CVS and soon in 2.3.8.

Ive just been alerted to a bug with email notifications in Elog.

Basically if your log book contains a space then the URL that is sent in 
emails when creating tickets or updating old entries doesnt put %20 (IEs 
space) inthe URL it leaves a space hense breaking the link.

for example

Correct Way prior to 2.3.8

http://192.168.0.1:99/Provisioning%20Request/35

Broken way with new version

http://192.168.0.1:99/Provisioning Request/35
                                 ^
Link is broken at this point

My config looks like this

Email Status Assigned = $Owner@abc.co.uk
Email Status Re-Assigned = $Owner@abc.co.uk
Email Status Completed = $Requester@abc.co.uk
Email "Send Update Email" Yes = $Requester@abc.co.uk
Use Email Subject = A Provisioning Ticket has been assigned to you or 
completed
Use Email From = NetworkTeam@abc.co.uk

> Correct Way prior to 2.3.8
> 
> http://192.168.0.1:99/Provisioning%20Request/35
> 
> Broken way with new version
> 
> http://192.168.0.1:99/Provisioning Request/35

Exactly this problem has been fixed between 2.3.7 and 2.3.8, so can it be 
that you mixed up these two versions? To be precise, the fix happend in 
Revision 1.113 from 2003/06/04 08:17:35. So are you sure that you use a 
version of elogd after that modification? I tried to reproduce your problem 
with the official 2.3.8 version, but I got the correct result.

> > Correct Way prior to 2.3.8
> > 
> > http://192.168.0.1:99/Provisioning%20Request/35
> > 
> > Broken way with new version
> > 
> > http://192.168.0.1:99/Provisioning Request/35
> 
> Exactly this problem has been fixed between 2.3.7 and 2.3.8, so can it be 
> that you mixed up these two versions? To be precise, the fix happend in 
> Revision 1.113 from 2003/06/04 08:17:35. So are you sure that you use a 
> version of elogd after that modification? I tried to reproduce your 
problem 
> with the official 2.3.8 version, but I got the correct result.

Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this 
upgrade, the only thing I kept was my own stylesheets and the config file.

One thing I just noticed is that if you dont have the URL statement set 
under global properties, some machines quote the hostname of the machine at 
which point this breaks the link. if you define the URL to the IP address 
the problem goes away.

However even without the URL setting undefined, it works for some people 
but not for others, I tried from 2 seperate machines and got 2 lots of 
results, so I suspect it might be DNS related somewhere along the lines.

> Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this 
> upgrade, the only thing I kept was my own stylesheets and the config file.
> 
> One thing I just noticed is that if you dont have the URL statement set 
> under global properties, some machines quote the hostname of the machine at 
> which point this breaks the link. if you define the URL to the IP address 
> the problem goes away.
> 
> However even without the URL setting undefined, it works for some people 
> but not for others, I tried from 2 seperate machines and got 2 lots of 
> results, so I suspect it might be DNS related somewhere along the lines.

The only place I can see this problem could arise from is the "Referer:" 
statement in the HTTP header. This is sent by the browser to elogd, so if the 
included URL contains a blank, this could cause the problem in case no "URL" 
statement is present in elogd.cfg. Can you please run "elogd -v" to see the 
communication betwen elogd and your browser and check this? Maybe it depends 
from the browser, or even from the history of previous accesses. If you 
confirm that the "Referer:" statement contains blanks, I can put in a fix.

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) 

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) 

Seems a stack problem.  I don't have an OS X box to validate my guess.  I've
made a Google search with the keywords: EXC_BAD_ACCESS stack "os x"

Perhaps the following reply [1] might help...

  How big are they? You're probably running into the default stack size 
  limit, which is 512 KB. Try `unlimit stacksize` in your shell before 
  running, which will give you 65536 KB per stack.

[1] http://zerowing.idsoftware.com/archives/gtkrad-macos/2003-January/000453.html