#196 Wrong service option installed into Windows registry

[Anonymous]

The wrapper.exe supports a -t option to run as Windows service. When running "wrapper -i path-to-wrapper.conf" to install a service, however, the ImagePath parameter is set to "wrapper -s path-to-wrapper.conf" - an invalid option. Running that command in a shell attempts to start the service, but fails. Running it with -t works fine.

This behavior goes back many versions.

[Leif Mortenson]

Logged In: YES
user_id=228081
Originator: NO

Thanks for taking the time to tell me about this. But this is the expected behavior.

The -s command tells the Wrapper.exe program that is being run by the Windows Service Manager. Most service applications make this the default when the application is run without parameters. I chose to use a parameter to signal this mode so the Wrapper could be run without parameters from the command line without blocking for a minute and giving an error.

The -i command tells the Wrapper.exe to launch in a mode which creates the registry entries necessary to register the service.

The -t command tells the Wrapper.exe to command the Windows Service Manager to start the service. The service manager then launches a SECOND instance of the Wrapper.exe application with the -s command. Once the service instance has started, the first instance reports that fact and exits.

Hope this makes sense.
Please let me know if you have any other questions.
Cheers,
Leif

[Nobody/Anonymous]

Logged In: NO

Okay, so apparently this -s parameter only works when in the service's ImagePath, whereas the -t parameter only works in the shell. Not sure why there are two different parameters, but this appears to be all working fine and the failures I was seeing come from something else.

It would still be nice to have the -s option documented somewhere to avoid such wild goose chases.

[Nobody/Anonymous]

Logged In: NO

Thanks for the clarification how the parameters work - very clear.