Tuesday, January 11, 2022

[389-users] Re: nsslapd-logging-backend

Hi there,

This feature is part of all 389 releases since, including on centos 7. Please note though, that journald support was removed, we now only support internal and syslog.

Hope that helps!

> On 12 Jan 2022, at 03:55, Xinhuan Zheng <xinhuan.zheng@gmail.com> wrote:
>
> We set up a few 389 Directory Server instances and set up replication among them. Each instance has its own internal logs. We need to centralize all the logs to one place by using syslog-ng. I learned a new configuration nsslapd-logging-backend - https://directory.fedoraproject.org/docs/389ds/design/logging-multiple-backends.html. According to RedHat documentation - https://access.redhat.com/solutions/3060901, the configuration is started in Redhat Enterprise Linux 7: 389-ds-base-1.3.5.10-11.el7. Is it started in CentOS 7 also?
>
> Xinhuan
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

--
Sincerely,

William Brown

Senior Software Engineer, Identity and Access Management
SUSE Labs, Australia
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

No comments:

Post a Comment