From: <mor...@us...> - 2004-02-19 16:06:31
|
Update of /cvsroot/wrapper/wrapper/src/documentation/xdocs/english In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22125/src/documentation/xdocs/english Modified Files: prop-ntservice-dependency-n.xml Log Message: Add a paragraph describing the known problem of the service manager ignoring the dependency tree on system shutdown. Index: prop-ntservice-dependency-n.xml =================================================================== RCS file: /cvsroot/wrapper/wrapper/src/documentation/xdocs/english/prop-ntservice-dependency-n.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** prop-ntservice-dependency-n.xml 31 Oct 2003 03:57:51 -0000 1.3 --- prop-ntservice-dependency-n.xml 19 Feb 2004 15:55:56 -0000 1.4 *************** *** 37,40 **** --- 37,51 ---- <screen format="linespecific"><![CDATA[wrapper.ntservice.dependency.1=MySQL]]></screen> </informalexample> + <para> + There is a known problem with dependency ordering when shutting + down or restarting the machine. For some reason, the Windows + Service Manager completely ignores the dependency tree and tells + all services to shutdown simultaneously. Depending on which + service gets the signal first, this can result in the services + being shutdown in a random order. This is a known problem with + all NT services and is not specific to the Java Service Wrapper. + Unfortunately there does not appear to be any way for the Wrapper + to work around this. + </para> <note> <para> |