Well, at least NSAPI allows you to write your own CGI handler,
which of course is a bit of a hassle.
Does the limit your refer to also prevent you from creating threads
with a stack bigger than 512KB in the CGI process?
Ulf
> > I think Jay misses the point. The question was how to get around the
> > 512K limit for the thread stack, not how to change the default setting
> > (which is 64K)
> Actually, the question was how to get around the 512 KByte hard & soft
> limits set with setrlimit(2) for the fork(2)'ed process which then
> exec(3)'s a CGI child. The thread stack size (set with StackSize in
> magnus.conf) is for Netscape server extensions, not CGI programs.
> The child stack limit is (on IRIX 6.2 at least) 512 KBytes, not 64
> KBytes. That's a different stack, internal to the server.
> I get the feeling that Netscape would rather we used WAI or server
> extensions --- in short, anything Netscape-specific. As far as I can
> see, there's no way to alter the CGI I/O timeout either.
> --
> Elliott Hughes - GeneData AG, Postfach 254, CH-4016 Basel, Switzerland
--
-------------------------------------------------------
Imperial College | Phone: +44 171 594 8249
Dept. of Computing | Fax: +44 171 581 8024
180 Queens Gate |
London SW7 2BZ, UK | http://www-dse.doc.ic.ac.uk/~ul
-------------------------------------------------------