You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ospackage/man/saptune-note.5
+11-7Lines changed: 11 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -56,13 +56,15 @@ Supported tags are:
56
56
.BI os= <os_version>
57
57
to define a special \fIosversion\fP
58
58
.br
59
-
Valid values for \fBos=\fP are the values from the \fBVERSION=\fP line of \fB/etc/os-release\fP, e.g. 12-SP5, 12, 15, 15-SP5 or 16.0
60
-
.br
61
-
To mark an entire major release the string 12-*, 15-* or 16.* can be used.
62
-
.br
63
-
Additional there is the possibility to use a list or a range of valid releases (service packs, dot releases)
59
+
Valid values for \fBos=\fP must match the value from the \fBVERSION=\fP line of \fB/etc/os-release\fP, e.g. 12-SP5, 12, 15, 15-SP5 or 16.0
60
+
61
+
If \fBVERSION=\fP contains spaces, only the string until the first space is used for comparison. This excludes any suffixes - like for beta versions - from the comparison.
62
+
63
+
To mark an entire major release the wildcard \fB*\fP in combination with a separator \fB-\fP or \fB.\fP (regardless of the one present in \fBVERSION\fP) can be used. Valid patterns are: 12-*, 12.*, 15-*, 15.*, 16-* or 16.*
64
+
65
+
Additional there is the possibility to use a list or a range of valid service packs or dot releases. Again the separator can be \fB-\fP or \fB.\fP (regardless of the one present in \fBVERSION\fP). And for service packs (in 12/15) the \fISP\fP prefix should be omitted.
64
66
.br
65
-
e.g 15-[2,4-5,6-,-7]
67
+
e.g 15-[2,4-5,6-,-7] or 15.[2,4-5,6-,-7]
66
68
.TP
67
69
.BI arch= <hardware_architecture>
68
70
to define a special \fIhardwarearchitecture\fP:
@@ -131,7 +133,9 @@ Example:
131
133
.BI virt= <virtualization type>
132
134
to define a special \fIvirtualization\fP class or type
133
135
.br
134
-
Valid class values for \fBvirt=\fP are \fBvm\fP, \fBchroot\fP and \fBcontainer\fP. Valid type values for \fBvirt=\fP are the output reported by \fI/usr/bin/systemd-detect-virt\fP
136
+
Valid class values for \fBvirt=\fP are \fBvm\fP, \fBchroot\fP, \fBcontainer\fP and \fBbare-metal\fP.
137
+
.br
138
+
Valid type values for \fBvirt=\fP are the output reported by \fI/usr/bin/systemd-detect-virt\fP. If no virtualization is detected it's concidered as \fBbare-metal\fP
@@ -474,11 +477,13 @@ This allows to create own Note definition files in \fI/etc/saptune/extra\fP. The
474
477
The editor is defined by the \fBEDITOR\fP environment variable. If not set editor defaults to /usr/bin/vim.
475
478
You need to choose an unique NoteID for this operation. Use '\fIsaptunenotelist\fP' to find the already used NoteIDs.
476
479
.TP
477
-
.Brefresh
480
+
.Brefresh\fBATTENTION:experimental\fP
478
481
Identifies and activates changed parameter settings of a Note definition. The changes get active without first reverting the 'old' settings, so the tuning of the system gets not interrupted.
479
482
480
483
ATTENTION:
481
484
.br
485
+
This action is currently in the state \fBexperimental\fP!
486
+
482
487
Currently only parameter of section "[sysctl]", "[sys]" and "[vm]" are supported by the \fIrefresh\fP action.
483
488
484
489
Parameter of section "[version]", "[rpm]", "[grub]", "[fs]" and "[reminder]" are only checked by saptune, but not applied. So there is nothing to do during refresh of a note and these sections are skipped without notice.
@@ -787,7 +792,7 @@ Same as a \fIsaptune note verify\fP
0 commit comments