Hi,
The short answer is: Yes. And as far as I am aware that's the only
solution. If you look at the actual command that runs, I guess it's
the fact it doesn't use localhost anymore.
3.1
[root@bdii00 ~]# ps -ef | grep slap
edguser 22859 1 0 10:45 ? 00:00:00 /usr/sbin/slapd -f
/opt/bdii/var/2171/bdii-slapd.conf -h ldap://localhost:2171 -u edguser
edguser 22993 1 0 10:46 ? 00:00:00 /usr/sbin/slapd -f
/opt/bdii/var/2172/bdii-slapd.conf -h ldap://localhost:2172 -u edguser
3.2
[root@bdii01 ~]# ps -ef | grep slap
edguser 18798 1 0 Mar25 ? 00:01:39 /usr/sbin/slapd -f
/opt/bdii/etc/bdii-slapd.conf -h ldap://bdii01.hep.ph.ic.ac.uk:2170 -u
edguser
Daniela
On 31 March 2010 09:55, Douglas McNab <[log in to unmask]> wrote:
> Hey Folks,
>
> I was comparing a new out of the box SL5 to SL4 BDII and noticed that the
> slapd process was denying connections to the SL5 BDII with the firewall off.
>
> The only way I could get the SL5 BDII to function properly was to add:
> slapd: ALL into hosts.allow
>
> Has anyone else seen this sort of behaviour? It does not seen to be
> documented anywhere.
>
> Cheers,
>
> Dug
> --
> ScotGrid, Room 481, Kelvin Building, University of Glasgow
> tel: +44(0)141 330 6439
>
--
-----------------------------------------------------------
HEP Group
Physics Dep
Imperial College
Tel: +44-(0)20-75947810
http://www.hep.ph.ic.ac.uk/~dbauer/
|