Update syntax that is no longer supported as of ldap-utils 2.5 release #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just a quick, very minor patch to convert the syntax into a format presently supported by ldap-utils 2.5+. With the new release, the -H flag now requires a full, standard URI and can no longer be used in conjunction with the -p flag listing the port number (-h can still be used for this purpose at the moment, but has already been deprecated).
Script currently breaks upon reaching this point and is resulting in many, many sad frogs in need of LDAP servers. Most of the company still seems to be relying on this incredibly amazing script, and this will get it back up and running smoothly as ever.
Thanks for taking a look Kfir and let me know if you have any questions or comments.