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

Add a parameter for Instance name in instsvc.exe [CORE673] #1039

Closed
firebird-automations opened this issue Feb 7, 2006 · 14 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Valdir Stiebe Junior (ogecrom)

Jira_subtask_outward CORE1565

SFID: 1426411#⁠
Submitted By: ogecrom

- Sorry if this is already planned, but I could not
find it. -

A parameter that will define part of the Service's and
registry entry's name.

With this I pretend to be able to install another
firebird instance just by:

1. copy the files to the destinationi location;
2. change the entry for listening port in firebird.conf
file;
3. execute instsvc.exe passing for it a string (i.e.
"Dype") do create the services and registry entries for
Firebird Server - DypeInstance and Firebird Guardian -
DypeInstance.

@firebird-automations
Copy link
Collaborator Author

Commented by: Alice F. Bird (firebirds)

Date: 2006-03-14 11:03
Sender: paul_reeves
Logged In: YES
user_id=110431

I'm wondering if we really need to accept this feature
request. We are not going to implement it for Fb 2.0 as we
are too close to final release.

The move to Firebird 3 will remove many of the reasons why
one might want to run two versions simultaneously. Fb 3 has
much greater configuration flexibility and will be able to
pass requests to different engine versions.

I'd recommend we set this as either 'postponed' or 'wont fix'.

@firebird-automations
Copy link
Collaborator Author

Commented by: Alice F. Bird (firebirds)

Date: 2006-02-11 13:34
Sender: ogecrom
Logged In: YES
user_id=443816

A remark I thought after posting this feature request.

This could be extended for instreg, and the server should
first look for the firebird.conf and aliases.conf in
registry by it instance name.

I think this is necessary because today (until fb1.5.3) I
must to delete the "Firebird Project" key to my new instance
use the correct firebird.conf.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

issuetype: New Feature [ 2 ] => Improvement [ 4 ]

SF_ID: 1426411 =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 2.1 [ 10041 ]

SF_ID: 1426411 =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Component: Installation [ 10012 ]

SF_ID: 1426411 =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

assignee: Dmitry Yemanov [ dimitr ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

resolution: Fixed [ 1 ]

assignee: Dmitry Yemanov [ dimitr ]

SF_ID: 1426411 =>

@firebird-automations
Copy link
Collaborator Author

Commented by: kkyy (kkyy)

please where i can to download this Fix Version ?

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

SF_ID: 1426411 =>

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

Verified by QA.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10697 ] => Firebird [ 15086 ]

@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
Projects
None yet
Development

No branches or pull requests

2 participants