Hello, > 1) > High Integration with SysV daemon structure: each mono service is a > different SysV daemon. > See Mathias previous post for an analysis of this option. > 2) > A unique SysV process which will be the MONO.SCM: each mono service will be > managed by these process. > See Mathias and Kai previous posts for an analysis of this option.
Remember that Mono is not tied to Linux, so using a solution which is cross-platform would be my recommended approach. So basically that means, rolling our own system to launch/shutdown processes. This has the added benefit, that a single daemon can be started, and we can have as much tight integration with this as we want. We can always have a `monoservices' init.d script for the SysV to launch, and this one in turn would load the definitions for Mono services from a Mono-controlled directory, but that way we minimize the integration work, and maximize flexibility. Love, Miguel _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
