https://bugzilla.redhat.com/show_bug.cgi?id=700627
Description of problem: The initial port number is hardcoded in the tools. They'd better be dynamically retrieved from the config file. # egrep 389 * bak2db.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); db2bak.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); db2index.pl: $indexes_list="ldapsearch $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -s one " . db2index.pl: $vlvindexes_list="ldapsearch $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -s sub -b \"cn=\"$instance\", cn=ldbm database,cn=plugins,cn=config\" \"objectclass=vlvIndex\" cn"; db2index.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); db2ldif.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); fixup-linkedattrs.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); fixup-memberof.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); ldif2db.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); ldif2ldap:ldapmodify -a -p 389 -D "$1" -w "$2" -f $3 monitor:ldapsearch -p 389 -b "$MDN" -s base "objectClass=*" ns-accountstatus.pl:$defport= "389"; ns-accountstatus.pl:$port= "389"; ns-activate.pl:$defport= "389"; ns-activate.pl:$port= "389"; ns-inactivate.pl:$defport= "389"; ns-inactivate.pl:$port= "389"; ns-newpwpolicy.pl:$opt_p = "389"; schema-reload.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); syntax-validate.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" ); usn-tombstone-cleanup.pl:open(FOO, "| ldapmodify $vstr -h <host> -p 389 -D \"$rootdn\" -w \"$passwd\" -a" );
set default ticket origin to Community
Added initial screened field value.
This has been fixed via ticket 528/332
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/47
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Duplicate)
Login to comment on this ticket.