[Mono-list] mod_mono strange behavior

Igor Georgiev gory@alphasoft-bg.com
Wed, 14 Jul 2004 11:08:42 +0300

 Apache/2.0.50 (Unix) mod_ssl/2.0.50 OpenSSL/0.9.7d PHP/4.3.7 mod_mono/1.0
mod_mono builded from cvs (present time Wed Jul 14 11:18:52 EEST 2004)

--- from httpd.conf
    MonoUnixSocket /tmp/mono/mod_mono_server
    MonoRunXSP True
    MonoExecutablePath /usr/local/mono/bin/mono
    MonoPath /usr/local/mono/bin
    MonoServerPath /usr/local/mono/bin/mod-mono-server.exe
    MonoWapiDir /tmp/mono

--- from apache error.log
[Wed Jul 14 11:09:58 2004] [error] Not running mod-mono-server.exe because
MonoListenAddress is present and there is no MonoListenPort.

---  from mod_mono man
              It  accepts  a  file  name as argument. That file will be a
named pipe used to send/receive data from/to
              mod_mono to/from mod-mono-server.
                    !!! <<< You cannot use MonoListenPort and MonoUnixSocket
at  the  same  time. >>> !!!
              Default value: "/tmp/mod_mono_server".

              TCP port on which mod-mono-server should listen/is listening
on. Mutually exclusive with MonoUnixSocket.
              When this options is specified, mod-mono-server and mod_mono
will use a TCP  socket  for  communication.
              Default value: none

              IP  address where mod-mono-server should listen/is listening
on. Can only be used when MonoListenPort is
              specified.  Default value: ""

My question is why mod_mono uses default MonoListenAddress when is not set
and instead MonoUnixSocket is set ???
Maybe quick fix in cvs needed :))


Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.719 / Virus Database: 475 - Release Date: 12.07.2004