On 1/27/21 12:53 PM, Angel Bosch wrote:
thanks for your response Mark,
I can see that two other options are removed. I used to configure retro-changelog like this:
dsconf myinstance plugin retrochangelog set --max-age 2d
dsconf myinstance plugin retrochangelog set --attribute nsuniqueid:targetUniqueId
Again I think you are looking at the older version of the server. The
current version has all these options:
$ dsconf localhost plugin retro-changelog set --help
usage: dsconf instance plugin retro-changelog set [-h] [--is-replicated
{TRUE,FALSE}] [--attribute ATTRIBUTE] [--directory DIRECTORY]
[--max-age MAX_AGE]
[--exclude-suffix EXCLUDE_SUFFIX]
optional arguments:
-h, --help show this help message and exit
--is-replicated {TRUE,FALSE}
Sets a flag to indicate on a change in the
changelog whether the change is newly made on that server or whether it was
replicated over from another server (isReplicated)
--attribute ATTRIBUTE
Specifies another Directory Server attribute
which must be included in the retro changelog entries (nsslapd-attribute)
--directory DIRECTORY
Specifies the name of the directory in which
the changelog database is created the first time the plug-in is run
--max-age MAX_AGE This attribute specifies the maximum age of any
entry in the changelog (nsslapd-changelogmaxage)
--exclude-suffix EXCLUDE_SUFFIX
This attribute specifies the suffix which will
be excluded from the scope of the plugin (nsslapd-exclude-suffix)
Mark
but now it doesn't accept those settings.
what's the correct way to configure that?
abosch
----- Missatge original -----
De: "Mark Reynolds" <mreynolds@xxxxxxxxxx>
Per: "General discussion list for the 389 Directory server project." <389-users@xxxxxxxxxxxxxxxxxxxxxxx>, "Angel
Bosch Mora" <abosch@xxxxxxxxxxxxxxxx>
Enviats: Dimecres, 27 de Gener 2021 14:43:19
Assumpte: [389-users] Re: plugin names and debian packages
Well 1.4.0 is quite old and is no longer maintained/supported. In
newer
versions of 389 it was changed to "retro-changelog". It probably was
changed in 1.4.1.
HTH,
Mark
On 1/27/21 5:41 AM, Angel Bosch Mora wrote:
hi!
I'm testing my install recipes on debian and I've found two little
problems.
on CentOS I execute
dsconf myinstance plugin retro-changelog enable
but today I tried in debian and it says is an invalid choice:
dsconf instance plugin: error: invalid choice:
'retro-changelog' (choose from 'memberof', 'automember',
'referint', 'rootdn', 'usn', 'accountpolicy', 'attruniq',
'dna', 'linkedattr', 'managedentries', 'passthroughauth',
'retrochangelog', 'whoami', 'list', 'get', 'edit')
So retro-changelog is called now retrochangelog.
Is that a Debian thing or it changed it's name on a recent version?
In addition I executed the command with the new name and it gives
me a message without a correct variable.
dsconf myinstance plugin retrochangelog enable
Enabled plugin '%s' Retro Changelog Plugin
dsconf myinstance plugin retrochangelog status
Plugin '%s' is enabled Retro Changelog Plugin
it seems a cosmetic error but I just want to be sure if I need to
open a bug.
here are the version of the packages:
dpkg -l | grep 389
ii 389-ds-base 1.4.0.21-1
amd64 389 Directory Server suite - server
ii 389-ds-base-legacy-tools 1.4.0.21-1
amd64 Legacy utilities for 389 Directory
Server
ii 389-ds-base-libs:amd64 1.4.0.21-1
amd64 389 Directory Server suite -
libraries
ii python3-lib389 1.4.0.21-1
all Python3 module for accessing and
configuring the 389 Directory Server
thanks in advance,
abosch
-- Institut Mallorqui d'Afers Socials. Aquest missatge, i si escau,
qualsevol fitxer annex, es dirigeix exclusivament a la persona que
n'es destinataria i pot contenir informacio confidencial. En cap
cas no heu de copiar aquest missatge ni lliurar-lo a terceres
persones sense permis expres de l'IMAS. Si no sou la persona
destinataria que s'hi indica (o la responsable de lliurar-l'hi) us
demanam que ho notifiqueu immediatament a l'adreca electronica de
la persona remitent. Abans d'imprimir aquest missatge, pensau si
es realment necessari.
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to
389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
--
389 Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to
389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
--
389 Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
