Skip to content
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.

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

doc: fix whitespace issues in admin guide #5854

Merged
merged 1 commit into from
Apr 3, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 10 additions & 9 deletions doc/guide/admin.rst
Original file line number Diff line number Diff line change
Expand Up @@ -666,15 +666,16 @@ components need to be configured, which is explained in the steps below.
"-e", "/usr/libexec/flux/flux-imp,run,epilog"
]

4. (optional) If log messages from the prolog or epilog are filling
up the broker logs, a list of ignore patterns may be added via
the ``[job-manager.perilog]`` ``log-ignore`` array. Each entry
in the array should be a :linux:man7:`regex`. POSIX extended
regular expression syntax is supported, e.g.:

.. code-block:: toml
[job-manager]
perilog.log-ignore = [ ".*Xauth.*", "^foo:.*debug" ]
4. (optional) If log messages from the prolog or epilog are filling
up the broker logs, a list of ignore patterns may be added via
the ``[job-manager.perilog]`` ``log-ignore`` array. Each entry
in the array should be a :linux:man7:`regex`. POSIX extended
regular expression syntax is supported, e.g.:

.. code-block:: toml

[job-manager]
perilog.log-ignore = [ ".*Xauth.*", "^foo:.*debug" ]

Note that the ``flux perilog-run`` command will additionally execute any
scripts in ``/etc/flux/system/{prolog,epilog}.d`` on rank 0 by default as
Expand Down