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

Security database has FW mode OFF, making it corrupted under some circumstances. [CORE1889] #2320

Closed
firebird-automations opened this issue May 8, 2008 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Was reporte dby Helen Borrie:

Someone was asking about corrupt security.fdb in the support list today. I checked my Fb 1.5 setup and sure enough, FW is off....so, to double-check, I restored the security.fbk from the v.1.5.5 root directory and that DB doesn't have FW on either.

Is there a reason why the security database can't have FW on?

Commits: e0e15ed 74fcaa0 eec2072

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Added build of gfix_static to boot build in order to be able to correctly set forced writes in security2.fdb. No use backporting in 1.5 - forced writes are anyway broken in it on linux.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.1.1 [ 10223 ]

Fix Version: 2.0.5 [ 10222 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

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