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

Jump to bottom

gsec Problem on XEON Maschine [CORE41] #365

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

gsec Problem on XEON Maschine [CORE41] #365

firebird-automations opened this issue Feb 14, 2004 · 7 comments
Assignees
@AlexPeshkoff
Labels
affect-version: 1.5 RC9 component: gsec priority: major resolution: cannot reproduce type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: speedybonsai (speedybonsai)

SFID: 897065#⁠
Submitted By: speedybonsai

Version 1.5 RC9.
I have an Bug with gsec, which is still there, like it was in
earlier versions to.
But it??s only on my XEON-Maschine.
System: SuSE Linux 8.2 (i586)
Kernel: 2.4.22
Proz.: Pentium III (Coppermine)
DUAL XEON 600 Mhz
on ServerWorks Motherboard

When I start gsec like:
gsec -user sysdba -password XXXX

it??s freezing. With Ctlr-C I can stop it, but I have to kill
the fbserver daemon. An regular stop is not possible.

On an normal PIII Maschine with the same Env.
everything is normal.
@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Version: 1.5 RC9 [ 10024 ]

Component: GSEC [ 10005 ]

assignee: Dmitry Yemanov [ dimitr ]

SF_ID: 897065 =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

assignee: Dmitry Yemanov [ dimitr ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10065 ] => Firebird [ 14237 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Do we have a reproducible sample for this case?

I suppose it should be closed, cause there were fixed so many MT/SMP related bugs, that this one sooner of all is also fixed.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Cannot Reproduce [ 5 ]

@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
Assignees

@AlexPeshkoff AlexPeshkoff

Labels
affect-version: 1.5 RC9 component: gsec priority: major resolution: cannot reproduce type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexPeshkoff @firebird-automations