one thing though... even with the larger stacksize, it still fails at the exact same point...
so there is a problem here...
[snip several hundred lines of output at least...so the server is getting a fair bit of initialisation done before it dies]
[09/Mar/2003:23:07:34][30118.1024][-main-] Debug: Loading packages/acs-mail/tcl/acs-mail-init.tcl...
[09/Mar/2003:23:07:34][30118.1024][-main-] Notice: Scheduling proc acs_mail_process_queue
[09/Mar/2003:23:07:34][30118.1024][-main-] Notice: acs-mail: ns_uuencode works!!
i notice that there is supposedly some patch for ns_uuencode to make it work with binary files... could it be a problem with that (in spite of the fact that the message above says ns_uuencode works)?
Or, perhaps it is failing on the step immediately after that one...
Could someone please start up their server with -f and -q options and tell me what the server does next, ie immediately after the lines that my server dies on ??
Maybe that will help work out what the problem is.
Im not sure whether it is worth wasting time trying to fix this error or whether it would be better to use the aolserver4 CVS which i just got. It built fine, but I will need to get nspostgres or configure it to work with postgres.so which i will do tomorrow.
If the aol4server CVS is not too hard to get working with openACS maybe that will be the way to go.
Thanks for any help. Im really quiet keen to have a look at the petri-net based openACS workflow package... with a working AOLsrver!