-
-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run as application not specifying switch -a #7637
Comments
Because support for Windows XP is dropped, "-a" can be made no-op at all. The only its purpose was to avoid long timeout on StartServiceCtrlDispatcher() call before returning ERROR_FAILED_SERVICE_CONTROLLER_CONNECT which is fixed in modern Windows versions. |
I don't think we should drop -a switch. As for
could you point me where it is described ? |
This is my own experience with dual application implementation years ago (when XP was the only option). As for "-a" switch: what do you expect it to do when it is used in service command line? It better to do nothing (but of course to be preserved for backward compatibility). |
Do you have such experience with Win7 or Vista ?
To do it, one must create service (or change existing service) manually, not using our instsvc. |
@hvlad |
I know no direct way. I going to handle
What both switches ? ;) There is no special switch to run as a service, if you about it. |
No. That's why I said that making "-a" switch obsolete is fine because WinXP is not supported anymore and the issue is fixed in later Windows. The delay could happen on WinXP which made "-a" switch useful that time, but since then it has no purpose. |
On Windows Firebird server could run as a service or as an application.
In the latter case command-line switch -a should be supplied, else "nothing happens" from user POV.
Actually, process starts and immediately finishes without notifying. This often confuses new users.
I propose to run Firebird as application if it was started by user (not by SCM) without switch -a.
The text was updated successfully, but these errors were encountered: