-
-
Notifications
You must be signed in to change notification settings - Fork 233
instance of fb_lock_manager runs after build [CORE107] #431
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
Comments
Modified by: @dyemanovpriority: Major [ 3 ] => Minor [ 4 ] Component: Build Issues / Porting [ 10070 ] SF_ID: 1475018 => |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => In Progress [ 3 ] |
Commented by: @AlexPeshkoff There is no use keep lock manager process running forever - reactivated old code to make it exit after timeout. |
Modified by: @AlexPeshkoffstatus: In Progress [ 3 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 Beta 1 [ 10141 ] SF_ID: 1475018 => |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 10131 ] => Firebird [ 14326 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Submitted by: @AlexPeshkoff
SFID: 1475018#
Submitted By: alexpeshkoff
fb_lock_manager remains running (from
../gen/firebird/bin/fb_lock_mgr) after build
process on linux
Commits: 38f48ed
The text was updated successfully, but these errors were encountered: