| Subject | Re: [firebird-python] Re: Linux 64 FB localhost connect trouble (re-posted from Support) |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-01-08T22:31:28Z |
At 02:29 PM 8/01/2005 -0800, you wrote:
account. You'll need a firebird group as well, with the firebird user in
it. I have encountered some Classic installs that overlooked the
group. Then the firebird group must have rwx on the data directories *and*
rw on the database files.
[snip]
I wrote:
the binaries and the symlinks in the /opt/firebird/lib directory. I've
always supposed that it was to make it so the installer merely had to copy
the symlinks into /usr/lib, without actually have to run a command to do
it. That said, it's never caused me any problems, either. I doubt that
it's the problem, or we would have heard the howls before now. Those 1.52
kits have been out for almost a month now.
The permissions seem the most likely source of the problem. I'm
particularly suspicious that you were able to *create* the firebird user,
because that seems to suggest that the installer didn't do that. Assuming
you used the rpm installer, I would guess you might be looking at a bug in
the installer script. If you "installed" it by just untarring, then all is
revealed!
This, btw, isn't a Python issue. If you remain stumped on this, I'd
suggest raising it in firebird-devel as an installer issue if you can't get
it going after a re-install. Nickolay Samofatov should be back from his
holidays some time next week.
Helen
> >The installation should have already set up the firebird user
>I've been running as root except when I tried running as firebird (for
>which I set up a linux user account).
account. You'll need a firebird group as well, with the firebird user in
it. I have encountered some Classic installs that overlooked the
group. Then the firebird group must have rwx on the data directories *and*
rw on the database files.
>I felt it was worth a shot.Understood.
>Please note that I've had none of these problems with a 32-bit install
>of CS on 32-bit Suse 9.1 on a 32-bit machine.
[snip]
I wrote:
> >Those should be symlinks.
> >There could be something there, in that your installation didn't install
> >libfbclient.so or, if it did, isql is not finding it for its attempt to
> >make local loopback connection.
> >
> >
>I was half hoping I wouldn't find it, but...libfbembed.so is in
>/opt/firebird/lib/, as well as /usr/lib64/.
>libfbembed.so.1 is inShould be symlinks too.
>/opt/firebird/lib/ and in /usr/lib64/,
>and libfbembed.so1.5.2 is in bothShould be the binary.
>directories as well.
>I don't know if this means anything or not.I don't know either. I've never quite understood why the kits place both
the binaries and the symlinks in the /opt/firebird/lib directory. I've
always supposed that it was to make it so the installer merely had to copy
the symlinks into /usr/lib, without actually have to run a command to do
it. That said, it's never caused me any problems, either. I doubt that
it's the problem, or we would have heard the howls before now. Those 1.52
kits have been out for almost a month now.
The permissions seem the most likely source of the problem. I'm
particularly suspicious that you were able to *create* the firebird user,
because that seems to suggest that the installer didn't do that. Assuming
you used the rpm installer, I would guess you might be looking at a bug in
the installer script. If you "installed" it by just untarring, then all is
revealed!
This, btw, isn't a Python issue. If you remain stumped on this, I'd
suggest raising it in firebird-devel as an installer issue if you can't get
it going after a re-install. Nickolay Samofatov should be back from his
holidays some time next week.
Helen