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

Accessing DB in invalid manner when links (hard or symbolic) are used for it [CORE4685] #4993

Closed
firebird-automations opened this issue Feb 7, 2015 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

The original issue was reported privately by Adriano - for aliases from databases.conf symbolic links are never expanded making it possible to attach to same file as if it's different databases.

But the impact of links is wider. First of all, not only symbolic, also hard links may be used in *nixes. And if we can solve the problem with symbolic links expanding them properly there is no way to understand that file names /one/name/file.fdb and /other/name.fdb may actually point to same inode, i.e. it's same file. Therefore we need wider use of files IDs (device + inode on it) already present in lock manager when comparing database names. This also affects analysis of file name in databases.conf when we need to determine correct configuration for that database.

Commits: 9a7c7a6 FirebirdSQL/fbt-repository@1f1c827

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Beta 2 [ 10586 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Cannot be tested

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

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