From: maruzz AT matrice DOT it (Giovanni Maruzzelli) Subject: Apache for NT, the REVENGE 13 May 1997 16:48:14 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Original-To: gnu-win32 AT cygnus DOT com Original-cc: Marc Cathomen In-Reply-To: <199705122134.OAA19168@cirdan.cygnus.com> Original-Sender: owner-gnu-win32 AT cygnus DOT com Hi there, read the manual, read the manual, read the manual, read the manual, read the manual, read the manual, read the manual. After a lot of tries, I've succeded in building Apache as a Service. And it work very well, when debugging it in console mode. Fast, reliable, also found how to substitute the signaling stuff that i'm not able to make works. Really a big satisfaction..... Just to discover that the services under NT have no right to fork children. So now there's an interesting case of software that is much more powerful in debugging mode (where as a console app can make how many children it want) than in production mode (where it is allowed one only process, the controlling one, that don't do nothing apart from starting and killing the others). Anyway, in the making of this, I've found that you can use thread (at least as a mean to receive events instead of using signals. Signals don't work for me). You can do that using win32 calls like CreateThread, OpenEvent, ExitProcess, etc.) Each process spawned can have a thread that wait for events .... So, any hints, apart from rewriting apache in multithreading mode? ciao, -giovanni *********************************************** * * * * * MATRICE srl * * Information Technology Solutions * * * * Giovanni Maruzzelli * * * * * * * * maruzz AT matrice DOT it * * http://www.matrice.it * *********************************************** - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".