The console depends on the directory server, which does not depend on systemd, but still acts as if it does. And since the directory server conflicts with slapd, and I need a ldap server to test the ldap client, and I need a ldap client to verify and test the server before moving it from my test machine, and . . .
On Mon, Aug 10, 2015 at 1:28 AM, Timo Aaltonen <tjaal...@debian.org> wrote: > On 01.08.2015 05:12, Ben Hildred wrote: > >> Package: 389-console >> Version: 1.1.7-2 >> Severity: serious >> Justification: Policy 9.11 >> >> 386-ds assumes systemd but does not include it in its list of >> dependencies. >> Further why does a ldap browser need to depend on init? >> >> [15/07/31:19:15:16] - [Setup] Info Error: command '/bin/systemctl --system >> daemon-reload' failed - output [] error [No such file or >> directory][15/07/31:19:15:16] - [Setup] Fatal Error: Could not create >> directory >> server instance 'crystal'. >> > > This comes from setting up the directory server, you're not trying to use > 389-console here.. > > -- -- Ben Hildred Automation Support Services 303 815 6721
