#144 documentation: Using non-default ports is trickier than suggested
Closed: wontfix 6 years ago Opened 12 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=185988

Description of problem:

This may not be the correct place to report this, but I couldn't fugure out
where to report documentation bugs for FDS.

Sections 1.2.1 and 1.2.3 of "Red Hat Directory Server 7.1: Red Hat Directory
Server Installation Guide" recommends running FDS under ports other than the
defaults.

While this may be correct the problem it presents is that there are a number of
places that the port needs to be specified other than just in the setup
program.

Places I have found so far include in ldap.conf and as a parameter to
ldapsearch.

I have specifically run into this while trying to follow:

http://directory.fedora.redhat.com/wiki/Howto:Samba

The maintainer of that doc stated that using the default ports was the
preferred
solution, suggesting that the install docs are incorrect.

I don't have an opinion on which way to do it, but if the install docs are
going
to continue to recommend using non-default ports, it would be helpful if they
also listed anywhere else the ports need to be specified.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

batch update moving tickets to future

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @nkinder:
- Issue set to the milestone: FUTURE

7 years ago

We use non-default ports in our tests regularly: closing works for me.

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to new (was: Needs Review)
- Issue close_status updated to: worksforme
- Issue status updated to: Closed (was: Open)

6 years ago

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/144

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: worksforme)

3 years ago

Login to comment on this ticket.

Metadata