I wrote:
>> I've got your symptoms when I've changed the primary host name in /etc/hosts
>> > from
>>
>> 127.0.0.1localhost localhost.localdomain
>>
>> to
>>
>> 127.0.0.1debian.example.org localhost localhost.localdomain
>>
>> Addind debian.example.org to /etc/hosts.equiv solved the problem.
>
Francesco P. Lovergine wrote:
> Uhm, incidentally that's no requirements about contents of /etc/hosts,
> but for a few old-days conventions. I would skip the hosts.equiv check
> with a suitable patch. It is basically a non-sense currently as all
> the rcommands related things...
I think I wasn't quite clear in my mail. Sorry.
Changing /etc/hosts as shown above causes the problem to trigger. To fix the
problem, the primary host name (the first on the 127.0.0.1 line, I beleive)
must be put in /etc/hosts.equiv
Yes, I agree this is stupid, but this is the current state of firebird 1.5.2. I
don't think this is fixed in 1.5.3. Maybe 2.0, but still not sure.
I suspect that fbserver process accepts control commands via its listening tcp
socket and needs some form of authentication of these control connections.
Probably it uses /etc/hosts.equiv for this, instead of using hard value of
127.0.0.1
As a workaround of the real issue, I can put some checks in
/etc/init.d/firebird2 to ensure that the primary hostname is in
/etc/hosts.equiv. It fould be better if fbserver responds to SIGxxx, but this
is not the case.
Thoughts?
dam
--
Damyan Ivanov Creditreform Bulgaria
[EMAIL PROTECTED] http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067 [EMAIL PROTECTED]/Gaim
signature.asc
Description: OpenPGP digital signature
