From 9da2c47ac52c86ae140a4d4587097696a00fc988 Mon Sep 17 00:00:00 2001 From: Luca Beltrame Date: Sun, 24 Jan 2016 00:40:49 +0100 Subject: [PATCH] Adjust description --- ...configure-389-ds-ldap-server-on-opensuse-tumbleweed.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2016-01-23-howto-configure-389-ds-ldap-server-on-opensuse-tumbleweed.markdown b/_posts/2016-01-23-howto-configure-389-ds-ldap-server-on-opensuse-tumbleweed.markdown index 8195929..e4a8a1b 100644 --- a/_posts/2016-01-23-howto-configure-389-ds-ldap-server-on-opensuse-tumbleweed.markdown +++ b/_posts/2016-01-23-howto-configure-389-ds-ldap-server-on-opensuse-tumbleweed.markdown @@ -52,7 +52,7 @@ zypper in 389-admin 389-admin-console 389-adminutil 389-console 389-ds 389-ds-co # Adjusting the configuration to ensure that it works -So far so good. But if you follow the guides now and use `setup-ds-admin.pl`, you'll get strange errors and the administration server will fail to get configured properly. This is because of a missing dependency on the `apache2-worker` package and because the configuration for the HTTP service used by 389 Directory Server is not properly adjusted for openSUSE: it references Apache 2 modules that the openSUSE package ships builtin and thus cannot be loaded. +So far so good. But if you follow the guides now and use `setup-ds-admin.pl`, you'll get strange errors and the administration server will fail to get configured properly. This is because of a missing dependency on the `apache2-worker` package and because the configuration for the HTTP service used by 389 Directory Server is not properly adjusted for openSUSE: it references Apache 2 modules that the openSUSE package ships builtin or with different names and thus cannot be loaded. Fixing the dependency problem is easy: