Steve,
Since they're threads, I assume they're sharing their memory? The
configuration I'm experimenting with may require as many as 100 XSP
processes running concurrently.
The threads of a certain process are sharing their memory.
If you plan to provide mass hosting for XSP, then you'll end up
running as many XSP processes as you have configured using
AddMonoApplications alias1..n
That's good to know... here's another - mod_mono would spawn XSP
servers using the Apache UID/GID, right? I'm trying to avoid that since
my company's customers are classically irresponsible with any type of
server-side scripting. ("How come I can't delete my files over FTP? I
uploaded them with my aspx script!!!")
What I've done is written a program that launches a separate XSP
process using the same UID/GID as is set by the suExecUserGroup
directive for each Apache virtual host. Also, the application roots are
set to the vhost document roots. This seems to keep the permissions in
line and perhaps adds some security, like using suexec.
How did you achieve that? mod_mono's code is still running under
the apache user, even if you supplied suExecUserGroup. Apache's
suEXEC stuff applies to CGI and SSI files only. That's the reason
why some PHP folks are using FastCGI for mass hosting.
Rob
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
