The runtime provides a number of configuration options for running
applications, for developping and debugging, and for testing and
debugging the runtime itself.
+.SH PORTABILITY
+On Unix-based systems, Mono provides a mechanism to emulate the
+Windows-style file access, this includes providing a case insensitive
+view of the file system, directory separator mapping (from \ to /) and
+stripping the drive letters.
+.PP
+This functionality is enabled by setting the
+.B MONO_IOMAP
+environment variable to one of
+.B all, drive
+and
+.B case.
+.PP
+See the description for
+.B MONO_IOMAP
+in the environment variables section for more details.
.SH RUNTIME OPTIONS
The following options are available:
.TP
precompiling code, you might want to compile with all optimizations
(-O=all). Pre-compiled code is position independent code.
.Sp
-Pre compilation is just a mechanism to reduce startup time, and avoid
-just-in-time compilation costs. The original assembly must still be
-present, as the metadata is contained there.
+Pre compilation is just a mechanism to reduce startup time, increase
+code sharing across multiple mono processes and avoid just-in-time
+compilation program startup costs. The original assembly must still
+be present, as the metadata is contained there.
+.Sp
+For more information about AOT, see: http://www.mono-project.com/AOT
.TP
.I "--config filename"
Load the specified configuration file instead of the default one(s).
.I "--help", "-h"
Displays usage instructions.
.TP
-.I "--optimize=MODE", "-O=mode"
+.I "--optimize=MODE", "-O=MODE"
MODE is a comma separated list of optimizations. They also allow
optimizations to be turned off by prefixing the optimization name with
a minus sign.
-O=all,-deadce,-inline
.fi
.TP
+.I "--runtime=VERSION"
+Mono supports different runtime versions. The version used depends on the program
+that is being run or on its configuration file (named program.exe.config). This option
+can be used to override such autodetection, by forcing a different runtime version
+to be used. Note that this should only be used to select a later compatible runtime
+version than the one the program was compiled against. A typical usage is for
+running a 1.1 program on a 2.0 version:
+.nf
+ mono --runtime=v2.0.50727 program.exe
+.fi
+.TP
.I "--security"
Activate the security manager (experimental feature in 1.1). This allows
mono to support declarative security attributes (e.g. execution of, CAS
The trace can be customized to include or exclude methods, classes or
assemblies. A trace expression is a comma separated list of targets,
each target can be prefixed with a minus sign to turn off a particular
-target. The words `program' and `all' have special meaning.
-`program' refers to the main program being executed, and `all' means
-all the method calls.
+target. The words `program', `all' and `disabled' have special
+meaning. `program' refers to the main program being executed, and
+`all' means all the method calls.
+.Sp
+The `disabled' option is used to start up with tracing disabled. It
+can be enabled at a later point in time in the program by sending the
+SIGUSR2 signal to the runtime.
.Sp
Assemblies are specified by their name, for example, to trace all
calls in the System assembly, use:
There are a number of external profilers that have been developed for
Mono, we will update this section to contain the profilers.
.PP
+The heap Shot profiler can track all live objects, and references to
+these objects, and includes a GUI tool, this is our recommended
+profiler.
+To install you must download the profiler
+from Mono's SVN:
+.nf
+ svn co svn://svn.myrealbox.com/source/trunk/heap-shot
+ cd heap-shot
+ ./autogen
+ make
+ make install
+.fi
+.PP
+See the included documentation for details on using it.
+.PP
The Live Type profiler shows at every GC iteration all of the live
objects of a given type. To install you must download the profiler
from Mono's SVN:
.PP
Then on each line the type is displayed as well as the number of bytes
that are being consumed by live instances of this object.
+.PP
+The AOT profiler is used to feed back information to the AOT compiler
+about how to order code based on the access patterns for pages. To
+use it, use:
+.nf
+ mono --profile=aot program.exe
+.fi
+The output of this profile can be fed back into Mono's AOT compiler to
+order the functions on the disk to produce precompiled images that
+have methods in sequential pages.
.SH CUSTOM PROFILERS
Mono provides a mechanism for loading other profiling modules which in
the form of shared libraries. These profiling modules can hook up to
various parts of the Mono runtime to gather information about the code
-being executed.
+being executed.
.PP
To use a third party profiler you must pass the name of the profiler
to Mono, like this:
.fi
.PP
The offsets displayed are IL offsets.
+.PP
+A more powerful coverage tool is available in the module `monocov'.
+See the monocov(1) man page for details.
.SH DEBUGGING
It is possible to obtain a stack trace of all the active threads in
Mono by sending the QUIT signal to Mono, you can do this from the
command line, like this:
.nf
+
kill -QUIT pid
+
.fi
Where pid is the Process ID of the Mono process you want to examine.
-The process will continue running afterwards.
+The process will continue running afterwards, but its state is not
+guaranteed.
+.PP
+.B Important:
+this is a last-resort mechanism for debugging applications and should
+not be used to monitor or probe a production application. The
+integrity of the runtime after sending this signal is not guaranteed
+and the application might crash or terminate at any given point
+afterwards.
.PP
You can use the MONO_LOG_LEVEL and MONO_LOG_MASK environment variables
to get verbose debugging output about the execution of your
passed to unmanaged code, and no references kept in managed code,
which will garbage collect the code. With this option it is possible
to track down the source of the problems.
+.TP
+.I "break-on-unverified"
+If this variable is set, when the Mono VM runs into a verification
+problem, instead of throwing an exception it will break into the
+debugger. This is useful when debugging verifier problems
.ne
.RE
.TP
this can be set to the name of a file system socket on which an egd or
prngd daemon is listening.
.TP
+.I "MONO_EVENTLOG_TYPE"
+Sets the type of event log provider to use (for System.Diagnostics.EventLog).
+.Sp
+Possible values are:
+.RS
+.TP
+.I "local[:path]"
+.Sp
+Persists event logs and entries to the local file system.
+.Sp
+The directory in which to persit the event logs, event sources and entries
+can be specified as part of the value.
+.Sp
+If the path is not explicitly set, it defaults to "/var/lib/mono/eventlog"
+on unix and "%APPDATA%\mono\eventlog" on Windows.
+.TP
+.I "win32"
+.Sp
+.B
+Uses the native win32 API to write events and registers event logs and
+event sources in the registry. This is only available on Windows.
+.Sp
+On Unix, the directory permission for individual event log and event source
+directories is set to 777 (with +t bit) allowing everyone to read and write
+event log entries while only allowing entries to be deleted by the user(s)
+that created them.
+.TP
+.I "null"
+.Sp
+Silently discards any events.
+.ne
+.PP
+The default is "null" on Unix (and versions of Windows before NT), and
+"win32" on Windows NT (and higher).
+.RE
+.TP
.I "MONO_EXTERNAL_ENCODINGS"
If set, contains a colon-separated list of text encodings to try when
turning externally-generated text (e.g. command-line arguments or
install. Or to the directory provided in the gacutil /gacdir command. Example:
.B /home/username/.mono:/usr/local/mono/
.TP
+.I "MONO_IOMAP"
+Enables some filename rewriting support to assist badly-written
+applications that hard-code Windows paths. Set to a colon-separated
+list of "drive" to strip drive letters, or "case" to do
+case-insensitive file matching in every directory in a path. "all"
+enables all rewriting methods. (Backslashes are always mapped to
+slashes if this variable is set to a valid option.)
+.fi
+.Sp
+For example, this would work from the shell:
+.nf
+
+ MONO_IOMAP=drive:case
+ export MONO_IOMAP
+
+.fi
+If you are using mod_mono to host your web applications, you can use
+the
+.B MonoSetEnv
+directive, like this:
+.nf
+
+ MonoSetEnv MONO_IOMAP=all
+
+.fi
+.TP
.I "MONO_MANAGED_WATCHER"
If set to any value, System.IO.FileSystemWatcher will use the default
managed implementation (slow). If unset, mono will try to use FAM under
managed implementation on error.
.TP
.I "MONO_PATH"
-Provides a search path to the runtime where to look for library files.
+Provides a search path to the runtime where to look for library
+files. This is a tool convenient for debugging applications, but
+should not be used by deployed applications as it breaks the assembly
+loader in subtle ways.
+.Sp
Directories are separated by the platform path separator (colons on unix). Example:
.B /home/username/lib:/usr/local/mono/lib
+.Sp
+Alternative solutions to MONO_PATH include: installing libraries into
+the Global Assembly Cache (see gacutil(1)) or having the dependent
+libraries side-by-side with the main executable.
+.Sp
+For a complete description of recommended practices for application
+deployment, see the
+http://www.mono-project.com/Guidelines:Application_Deployment page.
.TP
.I "MONO_RTC"
Experimental RTC support in the statistical profiler: if the user has
.Sp
The default is "win32".
.TP
+.I "MONO_TLS_SESSION_CACHE_TIMEOUT"
+The time, in seconds, that the SSL/TLS session cache will keep it's entry to
+avoid a new negotiation between the client and a server. Negotiation are very
+CPU intensive so an application-specific custom value may prove useful for
+small embedded systems.
+.Sp
+The default is 180 seconds.
+.TP
.I "MONO_THREADS_PER_CPU"
The maximum number of threads in the general threadpool will be
20 + (MONO_THREADS_PER_CPU * number of CPUs). The default value for this
custom serializer or a number to indicate when the XmlSerializer
should start serializing. The default value is 50, which means that
the a custom serializer will be produced on the 50th use.
+.TP
+.I "MONO_XMLSERIALIZER_DEBUG"
+Set this value to 1 to prevent the serializer from removing the
+temporary files that are created for fast serialization; This might
+be useful when debugging.
.SH ENVIRONMENT VARIABLES FOR DEBUGGING
.TP
.I "MONO_ASPNET_NODELETE"
as it forces all of the commands send to X11 server to be done
synchronously. The default mode of operation is asynchronous which
makes it hard to isolate the root of certain problems.
+.SH VALGRIND
+If you want to use Valgrind, you will find the file `mono.supp'
+useful, it contains the suppressions for the GC which trigger
+incorrect warnings. Use it like this:
+.nf
+ valgrind --suppressions=mono.supp mono ...
+.fi
.SH FILES
On Unix assemblies are loaded from the installation lib directory. If you set
`prefix' to /usr, the assemblies will be located in /usr/lib. On
Windows, the assemblies are loaded from the directory where mono and
mint live.
-.PP
-~/.mono/aot-cache
-.PP
+.TP
+.B ~/.mono/aot-cache
+.Sp
The directory for the ahead-of-time compiler demand creation
assemblies are located.
-.PP
-/etc/mono/config, ~/.mono/config
-.PP
+.TP
+.B /etc/mono/config, ~/.mono/config
+.Sp
Mono runtime configuration file. See the mono-config(5) manual page
for more information.
-.PP
-~/.config/.mono/certs, /usr/share/.mono/certs
-.PP
+.TP
+.B ~/.config/.mono/certs, /usr/share/.mono/certs
+.Sp
Contains Mono certificate stores for users / machine. See the certmgr(1)
manual page for more information on managing certificate stores and
the mozroots(1) page for information on how to import the Mozilla root
certificates into the Mono certificate store.
-.PP
-~/.config/.mono/keypairs, /usr/share/.mono/keypairs
-.PP
+.TP
+.B ~/.mono/assemblies/ASSEMBLY/ASSEMBLY.config
+.Sp
+Files in this directory allow a user to customize the configuration
+for a given system assembly, the format is the one described in the
+mono-config(5) page.
+.TP
+.B ~/.config/.mono/keypairs, /usr/share/.mono/keypairs
+.Sp
Contains Mono cryptographic keypairs for users / machine. They can be
accessed by using a CspParameters object with DSACryptoServiceProvider
and RSACryptoServiceProvider classes.
-.PP
-~/.config/.isolatedstorage, ~/.local/share/.isolatedstorage, /usr/share/.isolatedstorage
-.PP
+.TP
+.B ~/.config/.isolatedstorage, ~/.local/share/.isolatedstorage, /usr/share/.isolatedstorage
+.Sp
Contains Mono isolated storage for non-roaming users, roaming users and
local machine. Isolated storage can be accessed using the classes from
the System.IO.IsolatedStorage namespace.
+.TP
+.B <assembly>.config
+.Sp
+Configuration information for individual assemblies is loaded by the
+runtime from side-by-side files with the .config files, see the
+http://www.mono-project.com/Config for more information.
+.TP
+.B Web.config, web.config
+.Sp
+ASP.NET applications are configured through these files, the
+configuration is done on a per-directory basis. For more information
+on this subject see the http://www.mono-project.com/Config_system.web
+page.
.SH MAILING LISTS
Mailing lists are listed at the
http://www.mono-project.com/Mailing_Lists
.SH WEB SITE
http://www.mono-project.com
.SH SEE ALSO
-.BR certmgr(1), mcs(1), mint(1), monodis(1), mono-config(5), mozroots(1).
+.PP
+certmgr(1), mcs(1), monocov(1), monodis(1), mono-config(5), mozroots(1), xsp(1).
+.PP
+For more information on AOT:
+http://www.mono-project.com/AOT
.PP
For ASP.NET-related documentation, see the xsp(1) manual page
projects / mono.git / blobdiff