Have you written your script specifically as a service? On Windows a service has to communicate with the Service Control Manager(SCM). The Services GUI is just a way of asking the SCM to do things.
Think of the SCM as your Mother (OK, or Father) - when starting up you must tell her how long you are going to take over each startup phase, and if you take too long she panics and thinks you have died. That is what seems to have happened here. Did you specify a long enough period between each startup checksum? Did you remember to set the service status?
The SCM also asks you to do things from time-to-time (Suspend, Resume, Shutdown) or even if you are OK. Again, a failure to respond in a timely manner throws the old dear into a flap. | [reply] |
| [reply] |
yes I tried in google.
But couldn't get what to do?
| [reply] |
| [reply] |
A darned good reason to use the PDK from the good folks at ActiveState. With pretty much no knowledge of the internals of Windows (a state of blissful ignorance I choose to perpetuate) I have successfully written both services and tray apps, including a service with a tray app front end. Worth looking at.
jdtoronto | [reply] |
SRS service hung while Setup was trying to start it have you looked in the event logs that may point you in the right direction - I also agree that you should be using ActiveState tools - very helpful for stuff like this.
On windows you need to either compile it with ActiveState's PerlSvc, use Dave Roth's Win32::Daemon module or Jenda's Win32::Daemon::Simple module.
- cheers! | [reply] |
I used Win32::daemon to create and start a service.This service in turn runs a perl script .
When I start the service,the perl script is running well but because of the error ,the service is getting stopped automatically.
| [reply] |
| [reply]
[d/l] |
| [reply] |