diff options
| author | Luca Boccassi <luca.boccassi@microsoft.com> | 2021-11-04 20:48:58 +0100 |
|---|---|---|
| committer | Luca Boccassi <luca.boccassi@microsoft.com> | 2021-11-05 23:37:34 +0100 |
| commit | 82100ef486cf7e3b1df64b6bb29db43ac146ac6c (patch) | |
| tree | e4a211abc57f9266ff49b3369ef2694eda01f69d /man/systemd-analyze.xml | |
| parent | analyze: explain how the weight/range policy fields are used (diff) | |
| download | systemd-82100ef486cf7e3b1df64b6bb29db43ac146ac6c.tar.xz systemd-82100ef486cf7e3b1df64b6bb29db43ac146ac6c.zip | |
analyze: allow a custom policy to skip a check with weight=0
In some cases an offline analysis should ignore some fields, for example
a portable service in an image will never list RootImage/RootDirectory, as
they are added at runtime, and thus can be skipped.
Diffstat (limited to 'man/systemd-analyze.xml')
| -rw-r--r-- | man/systemd-analyze.xml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml index d3dfa9e526..e072d66131 100644 --- a/man/systemd-analyze.xml +++ b/man/systemd-analyze.xml @@ -1081,7 +1081,8 @@ Service b@0.service not loaded, b.socket cannot be started. normalized to the 1…100 range, and used to determine the overall exposure level of the unit. By allowing users to manipulate these fields, the 'security' verb gives them the option to decide for themself which ids are more important and hence should have a greater effect on - the exposure level.</para> + the exposure level. A weight of <literal>0</literal> means the setting will not be + checked.</para> <programlisting> { |