You could, presumably, write a task that enumerates through the running processes, finds the process in question (if it's still alive), and waits for it to disappear.
Let me ask the question this way: it would appear that this would be a general problem for your service. Does the Services control panel applet have a hard time issuing a Restart? Because that issues a Stop, and as soon as it's done, issues a Start. If the process is really still running, it won't be able to Start, because it's really still cleaning up. Maybe this is some flaw in the .NET service wrapper. I can't say I've ever seen it with unmanaged C++-based services (and I've definitely issued Restarts against a large variety of services, and they all behaved properly). - Brad On Wed, 01 Dec 2004 08:50:54 -0500, Hamza Zeen-Aldin <[EMAIL PROTECTED]> wrote: > That's exactly what's happening. but the problem is that there are no > PDB files, the code is in release mode. I have monitered the service, > processes, and threads when manually stopping the service. Windows takes > some seconds after the service is stopped to acctually remove the > service process from the task manager. Is there a way in Nant > servicecontroller to check if the service is completely stopped or I > would have to check if the service process is still running myself > through a script. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
