Accessing DB in invalid manner when links (hard or symbolic) are used for it
----------------------------------------------------------------------------
Key: CORE-4685
URL: http://tracker.firebirdsql.org/browse/CORE-4685
Project: Firebird Core
Issue Type: Improvement
Affects Versions: 2.5.3 Update 1, 2.1.7, 3.0 Beta 1, 2.5.3, 2.1.6, 3.0
Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 2.5.1, 2.5.0
Environment: posix
Reporter: Alexander Peshkov
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
