389-ds-base

#51154 Add stdout/stderr log output
Closed: wontfix by spichugi. Opened by firstyear.

Closed: wontfix
Reopen Issue

Issue Description

Related to the logging subsystem rewrite - for containers, log output should go to stderr/stdout so that the container engine can proxy those logs back to whatever collector is relevant. Similar, on linux if logs are written to these, they can be sent to journald (which is a bad idea though, because journald ratelimits and drops log events .....)

We should support stderr/stdout for logs for containers.

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4207

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.