Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 198540 - >=dev-db/firebird-2.0.3.12981.0-r2 - xinetd can't start lock manager
Summary: >=dev-db/firebird-2.0.3.12981.0-r2 - xinetd can't start lock manager
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: William L. Thomson Jr. (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-09 09:27 UTC by George Georgiev
Modified: 2007-12-05 00:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (emerge-info.txt,2.99 KB, text/plain)
2007-11-09 09:28 UTC, George Georgiev 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description George Georgiev 2007-11-09 09:27:46 UTC 
Server binaries are compiled with prefix /usr/share/firebird
this causes fb_inet_server to look for the lock manager in /usr/share/firebird/bin (which does not exists) and fail to start

Steps to reproduce:
  1.apply the dev-db/firebird-2.0.3.12981.0-r2.ebuild fixes from Bug #198538
  2.USE="xinetd" emerge =dev-db/firebird-2.0.3.12981.0-r2
  3.enable the firebird xinetd service
  4.try to connect to the firebird service
Result:
  Connect fails with "error reading data from connection"
  The firebird server process dies with
  "can't start lock manager: /usr/share/firebird/bin/fb_lock_mgr" error.
Expected result: 
  working firebird classic server

also applies to dev-db/firebird-2.0.3.12981.0-r3
Comment 1 George Georgiev 2007-11-09 09:28:05 UTC 
Created attachment 135555 [details]
emerge --info
Comment 2 William L. Thomson Jr. (RETIRED) gentoo-dev 2007-11-12 18:18:49 UTC 
Must have missed a path when I patched it, because it should be looking in /usr/bin. Will address ASAP
Comment 3 William L. Thomson Jr. (RETIRED) gentoo-dev 2007-12-05 00:06:25 UTC 
As I switched from patches to sed, I made sure that the path for fb_lock_mgr got updated. Fixed and committed to CVS, 2.0.3.*-r4 and 2.1.0.*r2. Closing bug, please reopen if problem persists. Thanks for reporting.