Thanks. I found out there is a new undocumented option -- [ns_info
pid] -- to return the server main process ID. We were using
[ns_thread getid] for this, but apparently that doesn't work from
scheduled procs in 3.4 (it works, but the process ID returned is not a
Linux process ID).
I'm starting from 3.4. I know I need to put in the AD patch for
killing the server completely when a fault occurs. That's been a
nagging problem for us all along.
Jim
>
> Jim Wilcoxson wrote:
> >
> > I'm working again on migrating to 3.x from 2.3.3 and could use some advice.
> >
> > 1. I downloaded the ArsDigita version - 3.3ad13 too. Are there any critical
> > fixes I need to put in 3.4 before using it for production? Or is 3.3ad13
> > better for production? Or...?
>
>
> various varsions of 3.3 had memory leak problems.
> you'd get leaks when interpreter threads
> expired. 3.4 fixes this. i would recommend using 3.4
> if possible.
