--- In firebird-support@yahoogroups.com, Michael Weissenbacher
<mw@...> wrote:

>
> Hi Herta,
> > I just created this file and afterwards started firebird: no

change,

> > same error message (and same delay).
> Please create a bug-report @.... Gentoo's firebird ebuild,

which was

> changed lately to comply to FHS, seems to be broken. I've got the

same problems

> here. Neither superserver nor classic does currently work with

Gentoo's ebuild.

> In the meantime just use the official release, not the Gentoo

ebuild.

>

Well, I don't quite know. First: in fact, on my machine the server
starts and runs (still using the gentoo ebuild and leaving all the
files where it installed them). This information may have been lost
in the course of the thread, I didn't repeat it in _every_ message.
If it truly doesn't work for you, that's quite another story. The
delay is a nuisance and the wrong message is a nuisance, but no
more.

Second: At first, I really couldn't start firebird after changing
the sysdba password. That's where the subject of this thread comes
from, I started it a little early. Then I found
the /etc/conf.d/firebird text file which still contained
the "masterkey" password. At this point I did create a bug-report,
because I couldn't really believe that the current sysdba password
belongs in such a text file, even if belonging to root and not
readable for others. This bug was immediately closed twice, so I
don't know if another report will have a better fate.

And third: at the moment I can't get Firebird 2.0 SuperServer to
start at all on Ubuntu 7.10. In this case it says "Ok", but doesn't
run and the log file only contains "INET/inet_error: connect errno =
111" - no starting message afterwards.

So I'm not even really certain that it's only a Gentoo problem. Or
both packages are broken in different ways.

Regards,
Herta