[Mono-list] Xsp in standalone amd mod_mono
Tue, 18 May 2004 10:28:32 -0400 (EDT)
Well, for one, the mod_mono module expects to see /tmp/mod_mono_server,
which is created by mod-mono-server.exe, not xsp.exe. If you did not chmod
the /tmp/mod_mono_server file, you will get Service Unavailable. Best
thing to do is script the mod-mono-server startup so that you pause for a
couple seconds after the .exe returns, then chmod the file in the script.
Also, unless they have got mod-mono-server.exe to recognize, drop, and
reload changed assembly DLLs, you will need to restart mod-mono-server.exe
each time you change an assembly DLL that the server has loaded. If you
don't, you will get some truly weird errors from your ASP.NET pages.
If you are serving ONLY ASPX pages on this server, then you don't need
Apache at all; just set up XSP to server port 80 and off you go (akin to
> I tried to add the --applications argument but xsp would throw an
> exception. With respect to the two being different, this I know but I
> would think that if xsp didnt work then most likely mod_mono would fail
> as well since they are using the same engine. Is this not correct. I
> would much rather get it to work as a module. The only reason I tried
> xsp as a standalone was so I could see why mod_mono was not servicing
> On Tue, 2004-05-18 at 10:14, Gregory Junker wrote:
>> Unless I missed some significant change in the past couple of weeks,
>> you should be doing the following to start the mod_mono server:
>> mono /usr/bin/mod-mono-server.exe --root <...> --applications
>> <...>:<...> --nonstop &
>> And then chmod the file so it's RW for the webserver.
>> XSP and mod-mono-server are not exactly the same thing...
>> Mono-list maillist - Monofirstname.lastname@example.org