Hi there,
In a scenario where I'm trying to setup a 389 Directory Server automatically, I ran into an issue with checking ports - no ports nor any networking, are available when I execute the setup. FWIW, I'm bootstrapping the setup for a live image.
The problem seems to be in ldap/admin/src/scripts/DSDialogs.pm, at line 69, which checks for the port to be available without taking into account whether or not the setup is supposed to continue (even without a port).
Attached is a patch.
Kind regards,
Jeroen van Meeuwen
On 04/21/2012 07:18 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
Hi there,
In a scenario where I'm trying to setup a 389 Directory Server automatically, I ran into an issue with checking ports - no ports nor any networking, are available when I execute the setup. FWIW, I'm bootstrapping the setup for a live image.
The problem seems to be in ldap/admin/src/scripts/DSDialogs.pm, at line 69, which checks for the port to be available without taking into account whether or not the setup is supposed to continue (even without a port).
Attached is a patch.
Kind regards,
Jeroen van Meeuwen
Thanks! Will be available in 1.2.11 To ssh://git.fedorahosted.org/git/389/ds.git fc6a0cd..f227f11 master -> master
-- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
389-devel@lists.fedoraproject.org