Hello, I have a Service Application (written in D6) that performs network operations over a socket connection (using Indy) that can be quite lengthy. As a result, it can take a long time to stop the service. The Service Control Manager however, is not very patient and promptly issues a "Service does not respond to the control function" message. After this, the service ends up in some unclear, uncontrollable state. I can avoid this timeout by setting the status property of the service to csStopped in the OnStop handler before waiting for all operations to be completed. But then I'm actually fooling the user by telling him he stopped the service, which is not yet true.
Is there a better solution? Peter Laman Senior Software Engineer Lance ICT Group Roermond, the Netherlands http://www.lance-safety.com - "A person is as young as his dreams and as old as his cynicysm" - Tony Campolo. __________________________________________________ Delphi-Talk mailing list -> Delphi-Talk@elists.org http://www.elists.org/mailman/listinfo/delphi-talk
