Skip to content
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

Service attachments (over presumably Xnet) fail when Classic started with -x -i parameters [CORE1017] #1428

Closed
firebird-automations opened this issue Nov 24, 2006 · 12 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Olivier Mascia (omascia)

Either run as an application or as a service, if the classic server (fb_inet_server.exe) is run with options -x -i (to restrict it to only tcp/ip and Xnet protocols), service attachments (with no server name, so presumably using Xnet) fail. The same attachments succeed when the server is started without "-i -x" options. The same attachments succeed, too, when the super-server is used, either with or without those "-i -x" command-line options.

Commits: 431cc7f 25bf9d6

@firebird-automations
Copy link
Collaborator Author

Modified by: Olivier Mascia (omascia)

description: Either run as an application or as a service, if the classic server (fb_inet_server.exe) is run with options -x -i (to restrict it to only tcp/ip and Xnet protocols), service attachments fail. The same attachments succeed when the server is started without "-i -x" options. The same attachments succeed, too, when the super-server is used, either with or without those "-i -x" command-line options. => Either run as an application or as a service, if the classic server (fb_inet_server.exe) is run with options -x -i (to restrict it to only tcp/ip and Xnet protocols), service attachments (with no server name, so presumably using Xnet) fail. The same attachments succeed when the server is started without "-i -x" options. The same attachments succeed, too, when the super-server is used, either with or without those "-i -x" command-line options.

summary: Service attachment fails when Classic started with -x -i parameters => Service attachments (over presumably Xnet) fail when Classic started with -x -i parameters

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 [ 10041 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 2.0.1 [ 10090 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

Reopened to update ticket information.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Closed [ 6 ] => Reopened [ 4 ]

resolution: Fixed [ 1 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Reopened [ 4 ] => Closed [ 6 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11350 ] => Firebird [ 15428 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment