> I suppose that the advice to increase Mac OS X's default stacksize limit
> might make a fine entry in the FAQ or README file.

I added a note in the installation instructions. 
(http://midas.psi.ch/elog/adminguide.html)

- Stefan

> Is there a way to configure elog so users that have their email notification
> on only get notified for updates to logs they have access to? I've looked
> all through the documentation and I can't seem to find a way to do this.

I guess you have a global password file and use "login user" statements for 
your logbooks. I have added some code which does per default not send any 
email to people who are not in the "login user" list, in case this list is 
present. New code under CVS. Please give it a try and let me know if it works 
for you.

- STefan

Is there a way to configure elog so users that have their email notification
on only get notified for updates to logs they have access to? I've looked
all through the documentation and I can't seem to find a way to do this.

If not is there some way I can work around this without to much trouble?  I
have lots of logs and would really hate to have to make configuration
changes in all of them .

Having the message body mailed to you is very convenient but some of my
users only get to see their logs. If the body gets mailed to them they get
to see everything anyway. 

When I had to use separate password files this wasn't an issue.

Sridhar & Recai,

Thanks to both of you for the rapid and effective advice.  Fixing the limit corrected my problem.  
I think I last got tripped up this way 10 years ago...

I suppose that the advice to increase Mac OS X's default stacksize limit might make a fine entry 
in the FAQ or README file.

Thanks again,
Joe 

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

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) 

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) 

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