Do we know when (if) this might make it to Centos 8 Streams?
Cheers.
389 Directory Server 2.0.13
The 389 Directory Server team is proud to announce 389-ds-base version 2.0.13
Fedora packages are available on Fedora 34, 35, and Rawhide
Rawhide:
that file.
It should be the same as in the default LDIF directory provided as an example.
The errors log file should have a more precise indication.
dsctl some-instance ldif2db userroot some-path/some-file.ldif
Thanks,
M.
On Thu, Dec 30, 2021 at 11:58 AM Joe Fletcher
mailto:jflet...@sscinc.com>>
for the 389 Directory server project.
<389-users@lists.fedoraproject.org>; Joe Fletcher
Subject: Re: [389-users] Re: Default browsing index generation
The e-mail below is from an external source. Please do not open
attachments or click links from an unknown or suspicious origin.
On 12
() missing 1 required positional argument: 'msg'
[root@m1 ~]#
On Wed, Dec 29, 2021 at 2:56 PM Joe Fletcher
mailto:jflet...@sscinc.com>> wrote:
Hi,
We’re looking at 389 DS v1.4. Is there an equivalent in the linux 8 cockpit to
the feature that used to exist in the v 1.3 management console su
Hi,
Is there something hard-coded into 389 v1.4 such that it can only import data
from /var/lib/dirsrv//ldif ?
I've been trying to initialize a new setup with an export we'd been using for
389 v1.3 but every time it failed with a "file not found" error until the ldif
was copied to
Hi,
We're looking at 389 DS v1.4. Is there an equivalent in the linux 8 cockpit to
the feature that used to exist in the v 1.3 management console such that it can
create default browsing indexes?
In the old GUI it was simply a case of right-click and go which did offer a
certain level of
Hi,
Does the native windows version of 389 management console keep logs of commands
executed and their results anywhere?
If not is there a way to make it do so?
I am working on a project to migrate to 389 and I have an instance whereby if I
select "restart directory server" from the tasks page
