Skip to content

Fixed journald typo #6556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ahardin-rh merged 1 commit into from
Nov 29, 2017
Merged

Fixed journald typo #6556

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions release_notes/ocp_3_7_release_notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -958,7 +958,7 @@ You can also automate the configuration of the provider to point to multiple Ope
[NOTE]
====
The *_/tmp/cp.yml_* file requires some manual configurations to create and use
it correctly.
it correctly.

//// Commenting out this section till CFME merges
See Multiple Container Providers for more information.
Expand Down Expand Up @@ -1023,9 +1023,9 @@ openshift_checks_output_dir=/tmp/checks
==== Jourald for System Logs and JSON File for Container Logs

Docker log driver is set to `json-file` as the default for all nodes. Docker
`log-driver` can be set to `journal`, but there is no log rate throttling with
journal driver. So, there is always a risk for denial-of-service attacks from
rogue containers.
`log-driver` can be set to `journald`, but there is no log rate throttling with
the journald driver. So, there is always a risk for denial-of-service attacks
from rogue containers.

Fluentd will automatically determine which log driver (`journald` or
`json-file`) the container runtime is using. Fluentd will now always read logs
Expand Down