saptune-3.1.3-150400.15.9.1 < > , x f p9| u\]>b!҃Py2yHzL}+%2LIwםXt.% d
{j6aT pqĂV`;s3n;Ut _R
M2
~Y,?c;B]W)pO&zY-7\CM! l*>dC͟ L?DG-Bsu%&*'
"Vz_Jj4[ n@;G_]^pm*x=$,@ > K $ ? d
W , 0 I j w & 3 7 z 9 z : z
; z =p z Wj z
W z Y z \6 z ^ ^ z ` ` a, bT ( b 8 b ' 9 cD ' : e ' = > ? @ F G z H z I z X \ Y h \ ݤ z ] ߌ z ^ b # c d N e S f V l X u l z v T
w ` z x H z y 0 z < L C saptune 3.1.3 150400.15.9.1 Comprehensive system tuning management for SAP solutions The utility adjusts system parameters such as kernel parameters and resource
limits to allow running various SAP solutions at satisfactory performance.
The utility can be used in place of sapconf. f mourvedre 4 SUSE Linux Enterprise 15 SUSE LLC GPL-3.0-only https://www.suse.com/ System/Management https://www.suse.com/products/sles-for-sap linux ppc64le
if [ -x /usr/bin/systemctl ]; then
test -n "$FIRST_ARG" || FIRST_ARG="$1"
[ -d /var/lib/systemd/migrated ] || mkdir -p /var/lib/systemd/migrated || :
for service in saptune.service ; do
sysv_service=${service%.*}
if [ ! -e /usr/lib/systemd/system/$service ] &&
[ ! -e /etc/init.d/$sysv_service ]; then
mkdir -p /run/systemd/rpm/needs-preset
touch /run/systemd/rpm/needs-preset/$service
elif [ -e /etc/init.d/$sysv_service ] &&
[ ! -e /var/lib/systemd/migrated/$sysv_service ]; then
/usr/sbin/systemd-sysv-convert --save $sysv_service || :
mkdir -p /run/systemd/rpm/needs-sysv-convert
touch /run/systemd/rpm/needs-sysv-convert/$service
fi
done
fi
if [ $1 -ne 1 ]; then
# package update
NOTEDIR=/usr/share/saptune/notes
if [ ! -d ${NOTEDIR} ]; then
# installed package version is < 2.0, update v1 to v3
# indicated by missing directory /usr/share/saptune/notes
# only change version to '1' (migration), if saptune is really used
# so check, if a solution or a note is defined
if (grep '^TUNE_FOR_SOLUTIONS[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1) && (grep '^TUNE_FOR_NOTES[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1); then
echo "saptune NOT configured and NOT used - version will be set to '3'"
else
echo "ATTENTION: saptune Version 1 is currently configured and used - but this version of saptune is no longer supported. Please migrate to Version 3 after the package update is done. saptune will stop working"
# to allow a migration from v1 to v3 after the installation, we need to preserve some 'old' data.
touch /tmp/update_v1tov3_saptune_inst || :
# preserve 'old' BOBJ and ASE note definition files for saptune
# version 1 compatibility
if [ -f /etc/saptune/extra/SAP_BOBJ-SAP_Business_OBJects.conf ]; then
cp /etc/saptune/extra/SAP_BOBJ-SAP_Business_OBJects.conf /etc/saptune/extra/SAP_BOBJ_n2c.conf
fi
if [ -f /etc/saptune/extra/SAP_ASE-SAP_Adaptive_Server_Enterprise.conf ]; then
cp /etc/saptune/extra/SAP_ASE-SAP_Adaptive_Server_Enterprise.conf /etc/saptune/extra/SAP_ASE_n2c.conf
fi
fi
else
# package version 2.0 or later
# check SAPTUNE_VERSION
stvers=$(grep ^SAPTUNE_VERSION= /etc/sysconfig/saptune | awk -F '"' '{ print $2 }')
if [ "$stvers" == 1 ]; then
# check, if saptune is really used
# so check, if a solution or a note is defined
if (grep '^TUNE_FOR_SOLUTIONS[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1) && (grep '^TUNE_FOR_NOTES[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1); then
# saptune NOT configured and NOT used
:
else
echo "ATTENTION: saptune currently running in Version 1 compatibility mode. Please migrate to Version 3 after the package update is done."
fi
fi
if [ ! -d /var/lib/saptune/working/sols ]; then
# installed package version is 2.x, update v2 to v3, save 'old' solution definition file
cp /usr/share/saptune/solutions /var/lib/saptune/.v2_solutions
fi
# special fix only for 3.0.0 installations
if [ -d /var/lib/saptune/working/sols ] && [ ! -f /usr/share/saptune/scripts/.updhelp ]; then
touch /tmp/update_fix_300_saptune_inst || :
fi
fi
# to prevent saptune related tuned error messages anytime after this
# saptune package installation switch off tuned to remove the 'active'
# saptune profile
# 'tuned-adm off' is sadly the only possibility to remove an 'active'
# saptune profile
systemctl -q is-active tuned && [[ $(cat /etc/tuned/active_profile 2>/dev/null) == saptune ]] && (echo "found active tuned with saptune profile"; touch /run/saptune_is_active_in_tuned; tuned-adm off) || :
# if the tuned profile is saptune, try to switch off tuned
# if 'tuned-adm off' before had worked, the profile is empty
# if not try again
[[ $(cat /etc/tuned/active_profile 2>/dev/null) == saptune ]] && (echo "found saptune as tuned profile, try to switch off tuned"; touch /run/saptune_is_active_in_tuned; tuned-adm off || systemctl stop tuned.service; > /etc/tuned/active_profile) || :
# if the tuned profile is still saptune, try to override the file
[[ $(cat /etc/tuned/active_profile 2>/dev/null) == saptune ]] && (echo "found saptune as tuned profile, override /etc/tuned/active_profile"; touch /run/saptune_is_active_in_tuned; systemctl stop tuned.service; > /etc/tuned/active_profile) || :
else
# initial installation
# check, if old config files from a former installation still exist
if [ -f /etc/sysconfig/saptune ]; then
mv /etc/sysconfig/saptune /etc/sysconfig/saptune.rpmold || :
fi
fi
touch /run/saptune_during_pkg_inst || :
PNAME=saptune
SUBPNAME=
SYSC_TEMPLATE=/usr/share/fillup-templates/sysconfig.$PNAME$SUBPNAME
# If template not in new /usr/share/fillup-templates, fallback to old TEMPLATE_DIR
if [ ! -f $SYSC_TEMPLATE ] ; then
TEMPLATE_DIR=/var/adm/fillup-templates
SYSC_TEMPLATE=$TEMPLATE_DIR/sysconfig.$PNAME$SUBPNAME
fi
SD_NAME=""
if [ -x /bin/fillup ] ; then
if [ -f $SYSC_TEMPLATE ] ; then
echo "Updating /etc/sysconfig/$SD_NAME$PNAME ..."
mkdir -p /etc/sysconfig/$SD_NAME
touch /etc/sysconfig/$SD_NAME$PNAME
/bin/fillup -q /etc/sysconfig/$SD_NAME$PNAME $SYSC_TEMPLATE
fi
else
echo "ERROR: fillup not found. This should not happen. Please compare"
echo "/etc/sysconfig/$PNAME and $TEMPLATE_DIR/sysconfig.$PNAME and"
echo "update by hand."
fi
# workaround for the missing directory.
mkdir -p /etc/security/limits.d
# cleanup 'typo' directory (bsc#1215969)
rm -rf /varlog || :
# handling of working area is the same for initial install or update
# initial install or update from v1 or v2 - STAGING is 'false' by default
# the entire content of package area gets copied directly to the working area
# which is empty at that state.
# update from v3 or later - STAGING may be 'true'
staging=$(grep ^STAGING= /etc/sysconfig/saptune | awk -F '"' '{ print $2 }')
if [ "$staging" == "true" ]; then
# handle staging area and DON'T touch the working area
touch /tmp/update_saptune_staging_area || :
else
# staging is NOT active, same behavior as with v2
# adjust the notes of an enabled solution, if needed
/usr/share/saptune/scripts/upd_helper enabledSol || :
if [ -f /var/lib/saptune/.v2_solutions ]; then
# remove no longer needed old solution definition file
rm -f /var/lib/saptune/.v2_solutions || :
fi
# set up working area
if [ -d /var/lib/saptune/working/notes ] || [ -d /var/lib/saptune/working/sols ]; then
rm -rf /var/lib/saptune/working/* || :
fi
mkdir -p /var/lib/saptune/working/notes || :
cp /usr/share/saptune/notes/* /var/lib/saptune/working/notes || :
mkdir -p /var/lib/saptune/working/sols || :
cp /usr/share/saptune/sols/* /var/lib/saptune/working/sols || :
fi
if [ $1 -ne 1 ]; then
# package update
# rewrite saptune version in /etc/sysconfig/saptune as fillup will not
# change variables
sed -i 's/SAPTUNE_VERSION="2"/SAPTUNE_VERSION="3"/' /etc/sysconfig/saptune
if [ -f /tmp/update_v1tov3_saptune_inst ]; then
# update from v1 to v3, same as v1 to v2 as nothing changed in v1
# step is needed to support migration after package update
/usr/share/saptune/scripts/upd_helper v1tov2pi || :
else
# update from v2 to v2 or higher, call update helper script in posttrans
touch /tmp/update_sle12tosel15_saptune_inst || :
# clean up some leftover files from older saptune v2 versions
/usr/share/saptune/scripts/upd_helper cleanup || :
fi
# special fix for update from 3.0.0 only
if [ -f /tmp/update_fix_300_saptune_inst ]; then
rm -f /tmp/update_fix_300_saptune_inst || :
/usr/share/saptune/scripts/upd_helper fix_300 || :
fi
#else
# initial install
fi
if [ -x /usr/bin/systemctl ]; then
test -n "$FIRST_ARG" || FIRST_ARG="$1"
[ -d /var/lib/systemd/migrated ] || mkdir -p /var/lib/systemd/migrated || :
if [ "$YAST_IS_RUNNING" != "instsys" ]; then
/usr/bin/systemctl daemon-reload || :
fi
for service in saptune.service ; do
sysv_service=${service%.*}
if [ -e /run/systemd/rpm/needs-preset/$service ]; then
/usr/bin/systemctl preset $service || :
rm "/run/systemd/rpm/needs-preset/$service" || :
elif [ -e /run/systemd/rpm/needs-sysv-convert/$service ]; then
/usr/sbin/systemd-sysv-convert --apply $sysv_service || :
rm "/run/systemd/rpm/needs-sysv-convert/$service" || :
touch /var/lib/systemd/migrated/$sysv_service || :
fi
done
fi
test -n "$FIRST_ARG" || FIRST_ARG="$1"
if [ "$FIRST_ARG" -eq 0 -a -x /usr/bin/systemctl ]; then
# Package removal, not upgrade
/usr/bin/systemctl --no-reload disable saptune.service || :
(
test "$YAST_IS_RUNNING" = instsys && exit 0
test -f /etc/sysconfig/services -a \
-z "$DISABLE_STOP_ON_REMOVAL" && . /etc/sysconfig/services
test "$DISABLE_STOP_ON_REMOVAL" = yes -o \
"$DISABLE_STOP_ON_REMOVAL" = 1 && exit 0
/usr/bin/systemctl stop saptune.service
) || :
fi
test -n "$FIRST_ARG" || FIRST_ARG=$1
if [ $FIRST_ARG -eq 0 ]; then
# Package removal, not upgrade
stvers=$(grep ^SAPTUNE_VERSION= /etc/sysconfig/saptune | awk -F '"' '{ print $2 }')
# revert settings
if (grep '^TUNE_FOR_SOLUTIONS[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1) && (grep '^TUNE_FOR_NOTES[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1); then
# saptune note configured and not used - nothing to do
:
else
# saptune configured and used - revert settings to clean up the system
if [ "$stvers" == 1 ]; then
saptune daemon revert >/dev/null 2>&1 || :
else
saptune service revert >/dev/null 2>&1 || :
fi
fi
# to suppress error messages from tuned, if the current active profile is
# the removed saptune profile
(systemctl -q is-active tuned && [[ $(cat /etc/tuned/active_profile 2>/dev/null) == saptune ]] ) && (tuned-adm off; /usr/sbin/saptune daemon stop >/dev/null 2>&1) || :
# if the tuned profile is saptune, try to switch off tuned
# if 'tuned-adm off' before had worked, the profile is empty
# if not try again
[[ $(cat /etc/tuned/active_profile 2>/dev/null) == saptune ]] && (> /etc/tuned/active_profile) || :
# clean up saved states left over
rm -rf /run/saptune/parameter/* /run/saptune/sections/* /run/saptune/saved_state/* || :
# clean up working and staging area
rm -rf /var/lib/saptune/staging/latest/* /var/lib/saptune/working/* /var/lib/saptune/working/.tmbackup || :
# preserve 'old' BOBJ and ASE note definition files for saptune
# version 1 compatibility
if [ -f /etc/saptune/extra/SAP_BOBJ-SAP_Business_OBJects.conf ]; then
echo "warning: /etc/saptune/extra/SAP_BOBJ-SAP_Business_OBJects.conf saved as /etc/saptune/extra/SAP_BOBJ-SAP_Business_OBJects.rpmsave"
mv /etc/saptune/extra/SAP_BOBJ-SAP_Business_OBJects.conf /etc/saptune/extra/SAP_BOBJ-SAP_Business_OBJects.rpmsave || :
fi
if [ -f /etc/saptune/extra/SAP_ASE-SAP_Adaptive_Server_Enterprise.conf ]; then
echo "warning: /etc/saptune/extra/SAP_ASE-SAP_Adaptive_Server_Enterprise.conf saved as /etc/saptune/extra/SAP_ASE-SAP_Adaptive_Server_Enterprise.conf.rpmsave"
mv /etc/saptune/extra/SAP_ASE-SAP_Adaptive_Server_Enterprise.conf /etc/saptune/extra/SAP_ASE-SAP_Adaptive_Server_Enterprise.conf.rpmsave || :
fi
# preserve saptune configuration, if saptune was used
# so check, if a solution or a note is defined
if (grep '^TUNE_FOR_SOLUTIONS[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1) && (grep '^TUNE_FOR_NOTES[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1) && (grep '^NOTE_APPLY_ORDER[[:space:]]*=[[:space:]]*""' /etc/sysconfig/saptune >/dev/null 2>&1); then
rm /etc/sysconfig/saptune || :
else
echo "warning: /etc/sysconfig/saptune saved as /etc/sysconfig/saptune.rpmsave"
mv /etc/sysconfig/saptune /etc/sysconfig/saptune.rpmsave || :
fi
fi test -n "$FIRST_ARG" || FIRST_ARG=$1
if [ $FIRST_ARG -eq 0 ]; then
# Package removal, not upgrade
test -n "$FIRST_ARG" || FIRST_ARG="$1"
if [ $1 -eq 0 ]; then
# Package removal
for service in saptune.service ; do
sysv_service="${service%.*}"
rm -f "/var/lib/systemd/migrated/$sysv_service" || :
done
fi
if [ -x /usr/bin/systemctl ]; then
/usr/bin/systemctl daemon-reload || :
fi
if [ "$FIRST_ARG" -ge 1 ]; then
# Package upgrade, not uninstall
if [ -x /usr/bin/systemctl ]; then
(
test "$YAST_IS_RUNNING" = instsys && exit 0
test -f /etc/sysconfig/services -a \
-z "$DISABLE_RESTART_ON_UPDATE" && . /etc/sysconfig/services
test "$DISABLE_RESTART_ON_UPDATE" = yes -o \
"$DISABLE_RESTART_ON_UPDATE" = 1 && exit 0
/usr/bin/systemctl try-restart saptune.service
) || :
fi
fi
fi u k , OY `_ -q / Y ' ~ ( g o ] l 8 u ~ d ~ { d $ { .8 ~ ] u .8 ] < e $ # % AAAAA큤큤A큤AA큤AA큤A큤A큤AAAAAAA f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f 466dc65201abca405e412ef24821d908be59120755e0d0bb45ef5a61f740c7b7 cb22b788963797df46672c1f525ed7fa8ec0ed34ab8104117359bcaf5673e227 bd013f3cfd82091ff2ce7a52d947d92a275e0a6e72b0b757617ef41da378d948 6b01558994a90661a0b9711a6a023342eb19aa66aa4cea7170ad7fc5730939ff 51b36adbf52cc1d4725044670fc463a3c5a33701c1682ca9630179c66d3c9969 69e8900a3516be4ab071e94bd2c8deafe6ef47cc7c12c65c35e76c5cb995dff3 d26e3cf627fed395f2280916c8bc072953a63b157558b4487ff7acbd1e407cc2 add538ca8f5923d27881b5c7486af6454475864bb96b98ea9aeb87fabb373c72 c77e065576be9b62467dbf14ec943460e1cad5cbf77962ad81a9c9ac34c02f1c a40dd73120e9a1be175fe88ed21bab1a38af441e092ddfc4e68d3882c171395a 604c1e5ae8746da0979c2ccd2216d35f3ccd854c31ec90b2eb75d2bb433a6de8 a72f4fe295e749ac0b436a7f4f04fb3629555462490172abad38564707a2569c 29398fc245fc6b15961b9d3c6f1fa787862444d21cda33219ec7f46734718066 a02bd1235f7718565b7e616f31e5c68ccf2a23db901b753e55e24a60fef5fe70 df609929a1a1d57bb5be2050e34a30bc76d9af7e87faa94037f5c847c377dd8f 50e6c7c857c78dd282d182b89856258dacb81bf76efaf30c7c938d5f0469131a dfc3580b12ea8298c62e6127042dd3a86dec49bca28cf12c4f2d7ca3a83eb692 ed2316a5f2d67772fde16dbad28a1a80ddb685a26585d6f1f46d70cf78d39408 7de76f18a958892229eaecf08aad137647801d1a765f794eaa4d21ea2e93a880 582bee83100eeba1ebd6824d1e188b5f7d616499cae66702ff63431f94ad8e3a d5b5c24fd7c3fdbc6300ed965808843c687ee77e4d5047400e6c51689ccb7c60 17c18c9494bcd40f1449fcb70904118f44af15f4a1c46331ba30dc2b24f4693e 6da6ae159c6b6ef21a7628305cdc247e23c4aa4eab0d4e9dcf7618415dc19888 f070db972d49cc503edf56c8cd88fe46d868450baef3beeb4a7a14529af5b432 75e21acf9a03788a461d98ce7ac84424e9b649f4e266ee89d5778c82aa526c82 0c893f44615f8781b604bcb33392e00e23a7bf81aff4a15a9b7a2c7330e3b026 cecc4d6477b7be44d61e48d9ae9882f13529bff6073d16eb26edaee3fa9a99d8 18cf3309d80ea5a24a16589479a19eafec3c42d1cc9557d9838bb481e1f4681d d0728fabf66a0c1160b773d79260bfc1001f0b621279f249ac16b41344997aec e3b325339855f561c44aedfdf5d898b965a2d4d4e4ba79630e870576ba581cca 5d83234df04604e094557d7b2180d932f20765c3ec68ae96f7e8a8e79485f3a6 43e0ee57754759be6047cc4e2ec3c4e0fdc27f18ffd4f9ab5ebb2384a250e5ae 7c99f20e7b3afd9ba1ebcf19cb790e057d7a76505fac175114b8833b8c5f49ce e6c5180d3db989e6ec5a91fb9c76a63d4369a1b9f9d0e95e73fe4a55a73ebf38 0a16f7eb370a3aeac0d112988d29adeeee865389fb54269edfd788197aa6ecdc 7b509aacbbc82068be5e4f3ef09c9c2a1858a3db7a4278236ad3f5604279a753 c232abf7cc01d74b879382ff4b623ac1bc6f90489f33784424e6bdf0422ac3ad fa8cbbca94289b366397a93a1c1988971120ca9aacbe29a279fb12b314739bb0 a776f90152cbdd7d1f5164d082eec8c40494b27c5eb51e7b5ab5c93a1ced93f8 66974fe470994353a99fc5a4bf4641c8a553d1bf69adb44dc1dddb08659e284a e3b23864d7e12b06a46053b99565569b0934b2c8585fceda159671e49c82539c a6fb3a7d1d3c69fe740224c8a3149a13208cb27064341583dba608422eefea1b 2f5250194dee28d7ece4404a52bb6fd1053bbf6bfa06649a91d03df8cc53b67e 51bb0d9393b23a13a12e5ac7cee942589c2b372b11cf587557a1b296c60320cd 7ba7eca81a140c8c47defdd8e869f617ace2a385efc57e10da9e5a73ecd832a1 227454d4ccf3fa479bf077a7a2f3cddb9d3b1cd2546761089d2d286eb9d1f371 568e014df652b8bdd8141d7efbda4eaa4edaaf831be5204c608326c781752a7c cd2394e466d410eb51542bc7563f740ab2ee0eea934eedd26d79c6addd3d26f6 434a8f30a8693dee62fdd2fdb6e012dd27bd9bc7ace73cb07d77dbbf7621f8aa 162abaf511d3c89b5ca9da9693a278f4d0a140708513d5327c3ce4e7c152f5a1 1fe5bd3b3c40f23462e6718cb796c179349ac0db2ef00ff570db28628a584715 c5488f83bdf271b560d0aaf7d6b7aa1e16977f707b1073b15abc71f2ea3ffabd 4e03a4ae6a4d19c81ab89e62db0fc92b023fd81edc35d61c5cf2b991b8505003 149c38e5c6cc114a11a944b698331133a226ea28afde6a06b4218fba210d6e66 d645fe42d21d7f2205c871ebd248a614212f604f71aaa7e4c5f63085ec587e0b 0e58c4cb7fee519eef1250fa247e8ca0c3e92b57c0bcf0d107af2d358536bdd8 682f0398fad7952732ff30b180be6b7967b12f1c15e8ca0e8fcf1ce078da2100 28cfe69eddef7aa43f8d711913cd9e3eec02ae287fec018951dacc9664e827a2 1f8c394024103ded05f277c147cff87ae86a92ef13600e177bdc3cc0f033b83d c6ec08cf371738f3d8febe101085b66edad8220392f3486428a26261bc6f2248 7704da0b0490f026cbba3e8b6a3eb993c179797457637b669d95738e47dec0b0 8139ebb49b1613e8bb670c8398331db76891b32e4664b441fb8be6bfd34d031d e1d5640ce938bddb2fd4cb0b4f3176c5bc599833854ab1d3779b28da6386bb76 fd2ce7d047babc794d2ef5bac77c7a325d1b398950054ffd66056aff6874c5ad 43e0ee57754759be6047cc4e2ec3c4e0fdc27f18ffd4f9ab5ebb2384a250e5ae 27eceaf2b30e822cf885e23ffbd929266ba65137e67ee3d6cd5e544af67ea09c 322639b22cdac9fc09b81a8f9b4faea692ca52c217b432f3f6eb3e788a198e2d 316050bcde054202f885f0c0f7014857c8510ca3fd3d993ff1a4c0aaa2664e74 f2f3ae32ba1a6627c8cf8c312248ddf2a1ab35e1b4c43619e2cc6d99e125e84e 90f02e9acde06b8fe5ee3803f85df3b37358f93a4a95d0af637e92b5a7351433 f871917fac9f0955b1394fea829af3abeb62afe6065ccdb0c4890c72381b2413 9ba817d9935f3179c13e66b6132e93ed732c01675b5bdf15227cf96eb951a77e 74768067dd68daf6b1bd015da87b4e85ab3bf82e9a41d5447af3344521b448cb 5a63c36a73aeb772d666f2cf918d53512bbd04f31494dc2555415674c6b425e3 936e3fe84597e8c5da581f205eeaf987415df857026469248580c78537264f2a d666f7c9a1c34dbca35c1e2308076c7421edf0174c6124847f7d7aeda17ed737 19f9e8ea1312c8bfd1567df3b71200b38e9aec4ba98380a4e534395511081fb7 2ad52b322104368243c42f51d27ec9d05510ed0043612e44f8e2768fbf01b142 bb73168f28a5910795483a4664726ab05b27baff804b7882a607f8ed1abf0a90 149c38e5c6cc114a11a944b698331133a226ea28afde6a06b4218fba210d6e66 d82a9db46df2461c8872cd4eef2e4670611ab9e709bedab1d50a75556facd5b5 d3d1040bfd8d777c887a08a25cf0b4190116929eeb841dcef3439b7583f22e90 9a53af82f2308ea848eecb545d69bb48dd12e40ada828701d5421fcfbbcdfbc3 4f4bf2daae98f1c1d41c1ae083c067d7743949dfc9b0057a1ffc0dff56bdcfd2 685eb085c3fb5c4291dd84ef8e0cf50c2bbe4ac66017b342115226027ee46c39 699707645af7d51706698de867190567fe2d748f4b94d568a7850772cc46a813 66c9704c571ddf11993c23a1c11fcffc780afd9b60ce7d77b4e3aa037f9deb53 b77435543815885d53a5b1d17604154bb3a342fd50101c35dd0fb827e8dca239 43e0ee57754759be6047cc4e2ec3c4e0fdc27f18ffd4f9ab5ebb2384a250e5ae 9d1dc42ad6ba5bcdd020b4595b2ab97fca7efcb435be1bde188db3530c557ee0 2aaac27dade3045a30c64834f4c1ce9f5a5a4864c43e547bec804bc6e0186f43 0a6af60fc7648d08bfd39ce750c7c7cc64be05a5ea9d4c5f0d20c737fa5796a9 aca1ca85e1a143b67c08994a460dfc2d30d4b9429eed3dda6b875f4dd8464505 c2e86cd543164f6cef8e0875da501b15eb66b2153f5b21d5463619ec5988e459 0307c7c98f749a714e61eef72dd73a130ead5a3631acbf72af427af778a080ac b403867c7456e434728993aceeb6048858bd09965d0fb80aa5a17e3e3e6fbdeb 848ad8c81e2ca099080424895fd32f2198803148ae9527057478b6ecfeb7e5c6 0e886d3da5cfac25167e8649845c43e462bd7a8b8eb33b6cc351be12607302b5 90362ddd12131a4a472db74c9f5753c54b6122993d69d19f8497e59bdb616a27 a2b9d45c2fe764cc84e60270794178535d8cdc165150a4abb551d4a2494abbcf 71a003f5d5656f9d9350a56df4237dcf33735d2e67b42034c31a33cc21d278f3 6c49fd25530eb0e046a764630ae7d89c679ae9e75e9c79032c3d15d21aac3cf6 service @ @ root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root saptune-3.1.3-150400.15.9.1.src.rpm config(saptune) saptune saptune(ppc-64) @ @
/bin/bash /bin/bash /bin/sh /bin/sh /bin/sh /bin/sh /usr/bin/cpupower /usr/bin/env /usr/bin/md5sum config(saptune) logrotate rpmlib(CompressedFileNames) rpmlib(FileDigests) rpmlib(PayloadFilesHavePrefix) rpmlib(PayloadIsXz) sysctl-logger sysstat systemd systemd systemd systemd systemd uuidd vim 3.1.3-150400.15.9.1 3.0.4-1 4.6.0-1 4.0-1 5.2-1 234-24.42 4.14.3 f~f-e̫@eB=d/@a aba?=@^U @^ @^
@]N@]X]@]@]4@]1]\-@[Ѱ@Z@Z|;Z3@Z1@Z.s@ZY|Y@YRHYY@X
@X)@X
@W@WWzOWQq@W!@abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com gboiko@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com hguo@suse.com abriel@suse.com abriel@suse.com abriel@suse.com abriel@suse.com hguo@suse.com hguo@suse.com hguo@suse.com hguo@suse.com hguo@suse.com hguo@suse.com hguo@suse.com - update package version of saptune to 3.1.3
* remove note 1868829 from solution S4HANA-APPSERVER as it is a
HANA DB note and was added by accident
(bsc#1226093)
* for verify and simulate output table - wrap content of the
columns 'actual', 'expected' and 'override', if they exceed a
width of 30 characters (e.g. net.ipv4.ip_local_reserved_ports)
* support inline comments in /etc/sysconfig/saptune
* change handling of the performance options.
Check, if the settings are supported in the get-Functions too.
This should fix the problem with some special Azure VMs
(E20d_v5) on newer SLES SPs
(jsc#SAPSOL-110)
* SAP Note 2578899 updated to Version 48
setting kernel.pid_max to 4194304 and
start sysctl-logger service - add require of package sysctl-logger for 15SP4 and 15SP5 too
(jsc#PED-6220) - update package version of saptune to 3.1.2
* to support setups with saptune monitoring and heavy automation
we limited the setting of our saptune lock to commands having
the potential to change anything in the system.
(bsc#1219500)
* fix timestamp in log messages of saptune
* remove redundant version information in header comment of
note definition files
* SAP Note 1656250 updated to Version 63
SAP Note 1771258 updated to Version 8
SAP Note 2382421 updated to Version 45
SAP Note 3024346 updated to Version 10
but without parameter value changes, only house keeping of the
version section and comment updates
* SAP Note 1984787 updated to Version 42
SAP Note 2578899 updated to Version 47
- add require of package sysctl-logger for 15SP6
(jsc#PED-5025) - update package version of saptune to 3.1.1
* typo in logfile directory name creates /varlog/saptune instead
of /var/log/saptune
(bsc#1215969)
* SAP Note 2382421
fix missing handling for Azure systems regarding parameter
'net.ipv4.tcp_timestamps'. This exclude setting was left out
during the last SAP Note update by mistake.
* add parameter IGNORE_RELOAD to /etc/sysconfig/saptune to
prevent saptune from stopping and starting the system tuning
during package update
Related to sapconf bug bsc#1209408.
- create a flag file in preinstall and remove it in posttrans of
the package installation to inform saptune that currently a
package installation/update takes place so that some special
situations can be handled as expected. - update package version of saptune to 3.1.0
* machine readable interfaces for saptune
add json output support
related json v1 schemas can be found after installation
on the system at /usr/share/saptune/schemas/1.0/
(jsc#PED-2194, jsc#PED-2195, jsc#SLE-23696)
* enhance the identification of the cloud service provider
(jsc#SLE-23779)
* add a command line syntax check
* colorized and filtered output for 'saptune note verify'
It is now possible to uses a 'color scheme' for the output to
highlight the non-compliant parameter or to limit the verify
output to show only non-compliant parameter.
(jsc#SLE-23727)
* add action 'saptune solution change' to switch to a new
solution even that another solution was already applied.
It's basically a 'revert OLDSOLUTION' && 'apply NEWSOLUTION'.
This will change the Note order in case of additional applied
Notes, but this is intended.
The confirmation for the revert of the old solution can be
suppressed by '--force'
(jsc#PED-2196)
* introduce a Trento naming convention for custom solutions in
the saptune man page to support trento checks.
(jsc#PED-4118)
* deprecate action 'saptune note|solution simulate'.
The action might get removed in a future saptune version
(jsc#PED-2199)
* deprecate support for the v1 vendor or custom specific Note
definition file format
(jsc#SLE-23725)
* detect virtualization environment by 'systemd-detect-virt' and
add the information to 'saptune status'.
(jsc#SLE-23885)
* enhance saptune with the new action 'check' to directly call
the external check script '/usr/sbin/saptune_check'.
(jsc#SLE-23726)
* de-deprecate the MAXDB solution definition. It is still active
supported by SAP.
And add solution NETWEAVER+MAXDB
(jsc#SLE-23724)
* support inline comments in the Note definition files
(jsc#SLE-23729)
* rework Note representation in 'saptune status' output
(jsc#SLE-24530)
* fix problem with 'verify' output, if a sysctl parameter is
empty on the system
(bsc#1199527)
* add hint to the manual page of saptune(8) regarding 'missing'
line feed for 'saptune note applied' and 'saptune note enabled'
It's intended.
(bsc#1193714)
* rework the version section to make it clear, which information
needs to be provided
(jsc#SLE-23722)
* add more information to 'saptune status':
differ between 'enabled' and 'applied' Solutions and add the
related Notes.
differ between Notes and Solutions in the staging area.
rename 'system state' line to 'systemd system state' to prevent
misunderstandings.
add virtualisation information.
* add tuning state to 'saptune status' output.
The check of the tuning state (an internal 'verify' operation)
can be skipped by using the flag '--non-compliance-check'.
In this case the tuning state will be reported as
unknown (checking disabled)
'saptune status' will exit with a return code of '4', if the
saptune service is enabled, the system is tuned, but the
tuning state is 'not compliant'.
(jsc#SLE-24928)
* add support for the IBM Power architecture to the vendor and
model section tagging
(jsc#SLE-23824)
* add new SAP Note 1868829 to set fs.aio-max-nr and add it to
the HANADB related solutions for SLE12 and SLE15.
* SAP Note 3024346 updated to Version 6
SAP Note 1557506 updated to Version 16
SAP Note 1656250 updated to Version 46
SAP Note 1805750 updated to Version 9
SAP Note 2161991 updated to Version 28
SAP Note 2205917 updated to Version 63
SAP Note 2382421 updated to Version 45
SAP Note 2534844 updated to Version 15
SAP Note BOBJ updated to Version 1
but without parameter value changes, only house keeping of the
version section and comment updates
* SAP Note 1984787 updated to Version 40
SAP Note 2578899 updated to Version 46
SAP Note 2684254 updated to Version 23
SAP Note 1680803 updated to Version 27
includes version 3.1 of 'SAP Applications on SAP Adaptive
Server Enterprise - Best Practices for Migration and Runtime'
* Solution 'SAP-ASE' changed - remove SAP Note 1410736.
The best practice document (version 3.1) for ASE was changed
and the SAP Note 1410736 is no longer referenced. Instead the
parameter 'net.ipv4.tcp_keepalive_time' is set in
SAP Note 1680803 (the ASE SAP Note) directly.
* introduce an additional parameter 'SKIP_SYSCTL_FILES' in the
/etc/sysconfig/saptune configuration file, which contains a
comma separated list of sysctl.conf files or directories
containing sysctl.conf files, which should be excluded from
the 'additional defined' WARNING messages.
Default is
SKIP_SYSCTL_FILES="/boot"
to skip the WARNINGS for '/boot/sysctl.conf-'
- check in preinstall and posttrans of the package installation,
if the active tuned profile is still 'saptune', even that this
profile no longer exists. If yes, try to remove it.
(bsc#1194688) - update package version of saptune to 3.0.2
- avoid excluding LVM slaves when getting valid block devices
(bsc#1194299)
- fix 'not compliant' state for energy_perf_bias on Power systems
and suppress misleading error message regarding missing 'mokutil'
(bsc#1193435)
- fix wrong behaviour of 'saptune revert all', if the saptune
service was stopped between the two commands 'apply' and
'revert all'
- 'saptune service enablestart|disablestop' now always perform
both actions and does no longer stop working, if the service is
already started|stopped.
(bsc#1193241)
- restrict the sys section of the AWS note 1656250 to the
availability of a nvme block device to support AWS x1e instances
too.
sys section definition of Note 1656250 changed.
(bsc#1192029)
- abandon the dependency to 'mokutil' by relying on sysfs to
detect a secure boot environment.
Related to bsc#1193435
- support /etc/fstab entries with 4 instead of 6 fields as these
are valid entries.
Change error handling from 'panic' to error log messages.
(bsc#1193580)
- enhance man page 'saptune.8'.
Add entry 'configured Note' and some more descriptions of the
entries from 'saptune service status'
(bsc#1192697)
- as the Power systems (hardware architecture 'ppc64le') does not
support files in '/sys/class/dmi' (this directory is not
available on the 'ppc64le' hardware architecture) some of our
section 'tags' will not work.
Add some additional log messages to identify the cause and add
a hint to the man page.
- fix block device settings (e.g. NRREQ) for multipath devices
(bsc#1193576)
- 'saptune verify' will now report a non existing sysctl or sys
parameter as 'not available on the system' (footnote) and this
parameter will not affect the compliance state.
But a warning is displayed to raise attention to may be typos in
the parameter name.
- 'saptune status' now reports the 'real' unit state, no mapping
of not running (inactive) service to simply 'stopped' any more.
(bsc#1194334) - update package version of saptune to 3.0.1
- fix the scheduler settings for multi path devices and
suppress missleading warning messages regarding vendor and model
information during block device detection
(bsc#1192460)
- fix override of custom solutions
(bsc#1192062)
- add missing update function for enabled solutions and add a
special fix to correct the 3.0.0 behavior
(bsc#1192053)
- saptune_check - degraded system is no longer considered an error
(bsc#1192272)
- log missing model and vendor information to the saptune log file
(bsc#1190509) - update package version of saptune to 3.0.0
This will be additional reflected in the saptune version found in
/etc/sysconfig/saptune (SAPTUNE_VERSION)
So now we will have saptune version 3
- saptune version 3
Strengthen configuration process with staging, checks of external
changes and expansion of automation to new platforms (Azure, AWS)
and hardware specifics
(jsc#SLE-21029 and jsc#SLE-20985)
- remove saptune version 1
(jsc#SLE-10823 and jsc#SLE-10842)
- remove usage of tuned from saptune
Add an own systemd service file for saptune to start/stop tuning
of parameter values during a reboot of the system.
Add a new saptune action 'service' to handle the saptune.service
supporting start/stop/enable/disable/status a.s.m.
The saptune action 'daemon', which handled tuned.service in the
past, is now flagged as 'deprecated' and internally linked to the
new action 'service'
(jsc#SLE-5589, jsc#SLE-5588, jsc#SLE-6457)
- add a sanity check to detect Note definition files which do not
exist anymore, because they were renamed or deleted, but without
reverting them before.
saptune will now print an error message, remove the Note from the
tracking variables in /etc/sysconfig/saptune and try to revert
the related parameter settings.
(bsc#1149205)
- check, if json input file is empty and handle some left-over
files from the migration from saptune v1 to saptune v2
(bsc#1167618)
- To support system parameters only relevant for specific SLES
releases, service packs and/or hardware architectures saptune
now supports 'tagged' sections inside the Note definition files.
(jsc#SLE-13246, jsc#SLE-13245)
- new kernel requirement for Power added to SAP-Note 2205917 and
2684254
SAP Note 2205917 updated to Version 61
SAP Note 2684254 updated to Version 15
(bsc#1167416)
- SAP Note 2382421 updated to Version 37
and move all 'not-well-defined' parameters from the 'reminder'
section into the 'sysctl' section, but with 'empty' values.
Use an override file to define the values fitting your system
requirements
(bsc#1170672)
- support empty parameter values in the Note definition files and
not only in the override file.
This is needed for the support of SAP Notes like 2382421, so that
the customer is able to simply use an override file to define
some special parameters instead of using a customer specific Note
definition file.
needed for bsc#1170672
(jsc#TEAM-1702)
- report an 'error' instead of 'info' and set the exit code to '1',
if we reject the apply of a solution
(bsc#1167213)
- Skip perf bias change if secure boot is enabled
When a system is in lockdown mode, i.e., Secure Boot is enabled,
MSR cannot be altered in user-space. So check, if Secure Boot is
enabled using the mokutil utility and skip setting the perf bias
in case it is.
(bsc#1176243)
- rework the internal block device handling to speed up the apply
of block device related tunings on systems with a high number of
block devices.
(bsc#1178207)
- change block device handling to handle multipath devices
correctly. Only the DM multipath devices will be used for the
settings, but not its paths.
(bsc#1179275)
- fixed wrong comparison used for setting FORCE_LATENCY
(bsc#1185702)
- add keyword 'all' to the 'rpm' section description in the man page
saptune-note(5)
(bsc#1182287)
- support note definition versions containing digits, upper-case
and lower-case letters, dots, underscores, minus and plus signs.
(bsc#1182289)
- fixed issue with 'verify' operation and parameter
'VSZ_TMPFS_PERCENT'. As this parameter is only used to calculate
the value of 'ShmFileSystemSizeMB' (if it is not set to a value
>0 in the Note definition file) it will not be checked and
compared during the saptune operation 'verify'. A footnote is
pointing this out.
(bsc#1182009)
- SAP Note 1771258 update nofile values
(bsc#1164720)
- SAP Note 2684254 updated to Version 20
SAP Note 2578899 updated to Version 39
SAP Note 1680803 updated to Version 26
- enhancements for saptune version 3
All jsc#TEAM-* entries mentioned below are related to this rework
(jsc#SLE-16972)
- Implement a lock to avoid multiple instances of saptune running
in parallel.
(jsc#TEAM-1700)
- Support for non-colorized output
If redirecting the output from saptune to a pipe, you no longer
need to deal with the 'ugly' control sequences for the colorized
output.
(jsc#TEAM-1679)
- Add enable/disable for systemd units and support all systemd unit
types in section [service]
(jsc#TEAM-1701)
- remove script /usr/share/doc/packages/saptune/sapconf2saptune
and the associated man page
(jsc#TEAM-1707)
- implement staging of Note definition file and solution
definitions.
The idea is to freeze the saptune configuration to avoid config
changes on package update when adding/removing/changing notes
or solutions within the package
(jsc#TEAM-1844)
- support custom solutions and override files for solutions.
Partners and customers will now be able to define their own
solution definitions by using files in /etc/saptune/extra
or to override the shipped solution definitions by using
override files in /etc/saptune/override
(jsc#TEAM-1706)
- support for device specific configurations
only supported for the [block] section, tags are 'vendor' and
'model' to support special block devices of a dedicated hardware
vendor or a dedicated hardware model
(jsc#TEAM-1728)
- add support for AZURE cloud (SAP Note 2993054)
(jsc#TEAM-2676)
- add support for AWS cloud (SAP Note 1656250)
(jsc#TEAM-1754 and jsc#TEAM-1755)
- add NVMe support to the block device handling to support AWS
(jsc#TEAM-2675)
- add SAP Note 3024346 (a NetApp note)
(jsc#TEAM-3454)
- rework daemon and service actions
(jsc#TEAM-3154)
- add support for 'read_ahead_kb' and 'max_sectors_kb' to the
[block] section
(jsc#TEAM-1699)
- add a warning to the reminder section of SAP Note 2382421
regarding iSCSI devices and setting of 'net.ipv4.tcp_syn_retries'
(jsc#TEAM-1705)
- for the actions 'note customise' and 'note create' check, if the
customer has changed something during the editor session.
If not, remove the temporary created note definition file.
(jsc#TEAM-825)
- add support for [sys] section
and handle double configurations for parameters defined in the
[sys] section
(jsc#TEAM-3342)
- check system sysctl config files as mentioned in the comments of
/etc/sysctl.conf and in man page sysctl.conf(5) for sysctl
parameters currently set by saptune notes. Print a warning and a
footnote for 'verify' and 'customize'.
(jsc#TEAM-1696)
- add support for [filesystem] section
only check filesystem mount options, not modify. Starting with
filesystem type 'xfs'
(jsc#TEAM-4093)
- add SAP Note 900929 for SAP Netweaver workloads.
It's the equivalent to the HANA Note 1980196.
(jsc#TEAM-4386)
- mv state files from /var/lib/saptune to /run/saptune to solve
the problem of state files surviving a reboot.
- add /sbin/saptune_check
- add the description of the solution definitions shipped with
saptune to the man page saptune(8)
(jsc#TEAM-4260) - update version of saptune v2 to 2.0.3
- changes to the UserTasksMax handling in saptune
In SLE15 the limit is removed from the systemd login manager and
therefore the setting is no longer supported in SLE15 by saptune.
On a system running SLE12 we do not restart the logind service,
but try to reload the new configuration after creating or
removing the drop-in file for UserTasksMax by using
'systemctl reload-or-try-restart systemd-logind'
as display managers do not like a restart of the logind service.
(bsc#1161791)
- add commands for listing enabled Notes/Solutions to saptune
(bsc#1160564)
- correct typo in the year in the man page headline of man page
saptune-note(5)
- SAP Note 1410736 updated to Version 6
correct typo net.ipv4.tcp_probes to net.ipv4.tcp_keepalive_probes - if a parameter is not supported by the system, the note action
'verify' will no longer report this as an error even if the value
is not compliant.
Additionally if there is a non compliant 'grub' parameter, which
has a compliant 'alternative' setting availabel (see man page
saptune-note(5) for details), the note action 'verify' will no
longer report this as an error
(bsc#1159671) - remove no longer needed and now misleading message at the end of
note action 'revert'.
- check, if sapconf service is available before disabling this
service during 'saptune daemon start'
(bsc#1156049) - add action 'delete' to the 'note' operation to delete a customer
or vendor specific Note definition file including the
corresponding override file if available.
A confirmation is needed to finish the action.
add action 'rename' to the 'note' operation to rename a customer
or vendor specific Note definition file to a new name. If a
corresponding override file is available, this file will be
renamed too. A confirmation is needed to finish the action.
If the Note is already applied, the action will be terminated
with the information, that the Note first needs to be reverted
before it can be deleted or renamed.
(jsc#SLE-9283) - Inform the customer that - by intention - the command
'saptune note customise '
does not apply changes immediately. It just changes the
configuration in the 'override' file. These changes have to be
applied in a second step.
This is explained in the man page saptune_v2(8) and a message is
printed in the logs and on the screen to inform the customer.
(bsc#1142467) - Add warning to man page, not to rename/remove/modify active
configurations
(bsc#1149002) - update version of saptune v2 to 2.0.2
- support multi-queue I/O scheduler for block devices
(bsc#1152598) - check, if the directory /etc/security/limits.d exists before
writing the limits drop-in file. If not, create it.
- add the '--no-pager' option to 'systemctl --list-unit-files' to
get all services at once.
- add missing search pattern to the update helper script to find all
old and superfluous notes during upgrade from SLE12 to SLE15
For the daemon operations do not exit with an error, if a note
definition file does not exist. Instead only log and print an
error message, but continue with applying the other notes
(bsc#1142526) - on 12SP1 and 12SP2 the directory /etc/security/limits.d may not
exist. So create the missing directory during postinstall of the
package. - update version of saptune v2 to 2.0.1
- update version of saptune v1 to 1.1.9 for migration purposes
- resetting all values to clean the system during package removal
- bugfixing saptune version 1:
fix saptune issues with /etc/security/limits.conf (bsc#1124485)
add deprecated message to the description of some notes
set scheduler for note SUSE-GUIDE-01 correctly (bsc#1123808)
No additional improvements or upgrades planned for saptune v1
For new features or current SAP Note settings please migrate to
saptune v2.
- support migration from saptune v1 to saptune v2
ship both versions of saptune in one package to support a
smooth migration controlled by the customer.
see man saptune-migrate(5) for more information
- support note name changes and note deletion during update of
saptune v2 from SLE12 to SLE15
- support different SAP Note definitions and solution definitions
related to the used operation system version
(distinguish between SLE12 and SLE15 at the moment)
- Remove calculation of optimized values, only set the values from
the configuration file irrespective of the current system value.
Current system value can be increase or decrease.
ATTENTION: saptune no longer respects higher system values.
Use the override option to change the values of the Note
definition files, if needed
(bsc#1124488)
- mark the Notes SUSE-GUIDE-01 and SUSE-GUIDE-02 as deprecated in
saptune v1 and remove these Note definitions from saptune v2
(bsc#1116799)
- add support helper script sapconf2saptune and the man page
- add new man pages saptune_v1.8, saptune_v2.8, saptune-note.5
and saptune-migrate.7
rewrite man page saptune.8
- add bash-completion for saptune
- add action 'show' to the 'note' operation to print content of
the note definition file to stdout
- add new action 'create' to support the customer/vendor while
creating a vendor or customer specific file in /etc/saptune/extra
using the template file /usr/share/saptune/NoteTemplate.conf
- simplify file name syntax for the vendor files available in
/etc/saptune/extra. Old file names still valid and supported.
Add header support (version, date, description) for the vendor
files available in /etc/saptune/extra as already available for
the note definition files in /usr/share/saptune/notes
- no longer write or remove entries from /etc/security/limits.conf.
Instead add or remove drop-in files in /etc/security/limits.d
The filename syntax for the drop-in files /etc/security/limits.d
is saptune--- -.conf
The limits entry syntax inside the Note definition files changed
to support more than one limits settings in the definition file
(bsc#1128322)
- preserve comment sections of the security limits file
/etc/security/limits.conf. Especially, if this is the only
content of the file.
(bsc#1124485)
- work with the current Note definition file to define the pagecache
settings and not with the default file
rename PAGECACHE_LIMIT_IGNORE_DIRTY to the correct sysctl name
vm.pagecache_limit_ignore_dirty
(bsc#1126220)
- setting of UserTaskMax is not done in the postinstall of the
package. It's now done by applying the related SAP Notes.
(bsc#1124489)
- starting to support severities INFO, WARNING, ERROR and DEBUG
for the logging and add a defined format for the log messages
- remove saptune as active tuned profile during action
'saptune daemon stop'
- start/stop services, if requested by SAP Notes, but do not
enable/disable these services
(bsc#1128325)
- adapt the parameter oriented save state file handling (store and
revert) to the special needs of the security limits parameter
(bsc#1124485)
- disable parameter settings using an override file (bsc#1124486)
- store the order of the note as they are applied to get the same
system tuning result after a system reboot as before
- correct the revert of the vm.dirty parameters by handling their
counterpart parameters in addition.
(bsc#1124487)
- adjust operation customize to the new configuration files and
override location and enable customize option for vendor and
customer specific files in /etc/saptune/extra
(bsc#1124487)
- Change output format of the operations list, verify and simulate
(bsc#1124487)
- Display footnotes during 'verify' and 'simulate'
(bsc#1124487)
- print current applied note order at the end of 'saptune note list'
and 'saptune note verify'
- remove Netweaver formula for page cache calculation. Use the
HANA approach '2% system memory' for both
- display a warning message, if a [block] section is found in the
Note definition file because on systems with a huge number of
block devices this operation may take some time
- Add force_latency handling to 'cpu' section.
Use the files in /sys/devices/system/cpu/cpu* instead of
/dev/cpu_dma_latency.
Remove the parameter from the tuned.conf file and add it to
the SAP note files '1984787' and '2205917'
- Add action 'saptune revert all' and add parameter based saved
state files to support proper revert functionality
(bsc#1124487)
- Add override file handling for the solution definition using
/etc/saptune/override/solution (bsc#1124486)
- Read solution definition from file /usr/share/saptune/solution
instead of static coding inside of saptune.
(bsc#1124486)
- tag deprecated solutions during list operation
- allow only ONE solution to be applied
- new solution definitions as discussed with SAP and Alliance team
- support solution names with '+'
- make sure a note, which is part of an applied solution definition,
but was reverted manually later, will NOT applied again after a
system reboot.
- One configuration file per SAP Note (bsc#1124486)
- add new SAP Notes and adapt content of SAP Notes
- Handle different locations of the new configuration files
(/usr/share/saptune/note, /etc/saptune/extra)
(bsc#1124486)
- Allow parameter override by the customer (bsc#1124486)
- Expand section handling of the 'ini file' handler to handle the
new configuration file entries. Supported sections:
version, reminder, login, mem, vm, block, limits, sysctl,
pagecache, cpu, service, rpm, grub
(bsc#1124486) - remove new line from println arg list of main.go to support newer
go versions.
(bsc#1120741)
- update version to 1.1.8 - never ever stop or disable uuidd.socket in saptune (bsc#1100107)
- update version to 1.1.7 - correct content of /etc/systemd/logind.conf.d/sap.conf.
(bsc#1089864)
- improve error messages and exclude special block devices
from 'number of request' settings. Improve the verify option for
the block devices.
(bsc#1079599) - Fix a typo in package description. (bsc#1053374)
- Update from version 1.1.3 to 1.1.4 - Start to support multiqueue schedulers.
Writing a message to the log file, if a block device does not
support the choosen scheduler.
(bsc#1072562) - Check, if pagecache limit is available at the system. If yes, add
SAP note 1557506 to the note list and the solution definition of
saptune. If not, skip SAP note 1557506 silently
(bsc#1071539, fate#323778) - Skip using tuned-adm command inside of saptune. Instead write
'saptune' profile directly to /etc/tuned/active_profile and
enable and start the tuned service
Remove the workaround for the tuned problem with section [cpu]
(bsc#1060514) - workaround for a tuned problem with section [cpu]
(bsc#1060514) - support customer entries in /etc/security/limits.conf containing
values like 'unlimited' instead of an integer value.
(bsc#1060469)
- change error handling and redirect error messages to stderr instead
of stdout. (bsc#1050521) - Fix a typo in package description.
(bsc#1053374) - Amend logind's behaviour
(bsc#1031355, bsc#1039309, bsc#1043844) - update man page to reflect the changes for bsc#1026172 - add solution SAP ASE (Sybase) and SAP Business OBJects (BOBJ)
according to fate#320359. - Support of vendor specific tune files located in /etc/saptune/extra
(bsc#1026172). - Tune a PowerPC little endian system in a way similar to x86 system.
Bump version to 1.0.5 to fix (bsc#1009529). - Fix processing of CLI parameter "--help" (bsc#1006114).
- Fix startup failure caused by absence of sapconf package (bsc#1006187). - Avoid conflicting with sysconfig path of sapconf. (bsc#988186)
Bump versin to 1.0.3. - Remove conflict against sapconf to resolve
bsc#988186.
Bump version to 1.0.2. - Exclusively build on X86_64 and PPC64le.
Continue with fate#320360, fate#320361, fate#320362, fate#320633. - Remove ExclusiveArch.
- Control uuidd as part of the tuning process.
- Minor changes in the wording of CLI program output.
- saptune conflicts with sapconf.
- Bump version to 1.0.1.
- fate#320360, fate#320361, fate#320362, fate#320633. - First revision.
Implement fate#320360, fate#320361, fate#320362, fate#320633. /bin/sh /bin/sh /bin/sh /bin/sh mourvedre 1722223560
! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z 3.1.3-150400.15.9.1 3.1.3-150400.15.9.1 3.1.3-150400.15.9.1
saptune saptune extra override supportconfig plugins saptune saptune.service rcsaptune saptune saptune_check saptune sysconfig.saptune saptune-note.5.gz saptune-migrate.7.gz saptune.8.gz saptune NoteTemplate.conf SolutionTemplate.conf deprecated notes 1410736 1656250 1680803 1771258 1805750 1868829 1980196 2161991 2382421 2534844 2578899 2684254 2993054 3024346 900929 941735 SAP_BOBJ schemas 1.0 saptune_check.schema.json saptune_daemon_start.schema.json saptune_daemon_status.schema.json saptune_daemon_stop.schema.json saptune_help.schema.json saptune_invalid.schema.json saptune_lock_remove.schema.json saptune_log_set.schema.json saptune_log_status.schema.json saptune_note_applied.schema.json saptune_note_apply.schema.json saptune_note_create.schema.json saptune_note_customise.schema.json saptune_note_customize.schema.json saptune_note_delete.schema.json saptune_note_edit.schema.json saptune_note_enabled.schema.json saptune_note_list.schema.json saptune_note_rename.schema.json saptune_note_revert.schema.json saptune_note_revert_all.schema.json saptune_note_revertall.schema.json saptune_note_show.schema.json saptune_note_simulate.schema.json saptune_note_verify.schema.json saptune_revert_all.schema.json saptune_service_apply.schema.json saptune_service_disable.schema.json saptune_service_disablestop.schema.json saptune_service_enable.schema.json saptune_service_enablestart.schema.json saptune_service_reload.schema.json saptune_service_restart.schema.json saptune_service_revert.schema.json saptune_service_start.schema.json saptune_service_status.schema.json saptune_service_stop.schema.json saptune_service_takeover.schema.json saptune_solution_applied.schema.json saptune_solution_apply.schema.json saptune_solution_change.schema.json saptune_solution_create.schema.json saptune_solution_delete.schema.json saptune_solution_edit.schema.json saptune_solution_enabled.schema.json saptune_solution_list.schema.json saptune_solution_rename.schema.json saptune_solution_revert.schema.json saptune_solution_show.schema.json saptune_solution_simulate.schema.json saptune_solution_verify.schema.json saptune_staging_analysis.schema.json saptune_staging_diff.schema.json saptune_staging_disable.schema.json saptune_staging_enable.schema.json saptune_staging_is-enabled.schema.json saptune_staging_list.schema.json saptune_staging_release.schema.json saptune_staging_status.schema.json saptune_status.schema.json saptune_version.schema.json scripts .updhelp upd_helper sols BOBJ.sol HANA.sol MAXDB.sol NETWEAVER+HANA.sol NETWEAVER+MAXDB.sol NETWEAVER.sol S4HANA-APP+DB.sol S4HANA-APPSERVER.sol S4HANA-DBSERVER.sol SAP-ASE.sol saptune staging latest working notes sols saptune /etc/logrotate.d/ /etc/ /etc/saptune/ /usr/lib/ /usr/lib/supportconfig/ /usr/lib/supportconfig/plugins/ /usr/lib/systemd/system/ /usr/sbin/ /usr/share/bash-completion/completions/ /usr/share/fillup-templates/ /usr/share/man/man5/ /usr/share/man/man7/ /usr/share/man/man8/ /usr/share/ /usr/share/saptune/ /usr/share/saptune/notes/ /usr/share/saptune/schemas/ /usr/share/saptune/schemas/1.0/ /usr/share/saptune/scripts/ /usr/share/saptune/sols/ /var/lib/ /var/lib/saptune/ /var/lib/saptune/staging/ /var/lib/saptune/working/ /var/log/ -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g obs://build.suse.de/SUSE:Maintenance:34745/SUSE_SLE-15-SP4_Update/66808ab9302d2957d845d9fce2515396-saptune.SUSE_SLE-15-SP4_Update drpm xz 5 ppc64le-suse-linux ASCII text directory Bourne-Again shell script, ASCII text executable ELF 64-bit LSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, stripped Bourne-Again shell script, UTF-8 Unicode text executable, with very long lines troff or preprocessor input, ASCII text, with very long lines (gzip compressed data, max compression, from Unix) troff or preprocessor input, UTF-8 Unicode text (gzip compressed data, max compression, from Unix) UTF-8 Unicode text Windows setup INFormation, ASCII text R R R &m3SLan(# Use a real bash script with an explicit "exit 0" at the end to be by default fail safe
# an explicit "exit 1" must be use to enforce package install/upgrade/erase failure where needed
# Begin refresh systemd units and clean up possibly obsolete systemd units
# The following is a generic way how to refresh and/or clean up systemd units.
# A systemd unit may need a refresh after updating a package when the new package
# had installed a changed systemd unit file for an enabled systemd unit.
# A systemd unit may become obsolete by updating a package (see bnc#904215).
# A systemd unit is considered to have become obsolete when the systemd
# symlink /etc/systemd/system/.../unit_name -> /path/to/unit_file is broken.
# When during package update the new package does no longer provide a unit file
# then the systemd symlink becomes broken after the files of the old package
# had been actually removed by RPM.
# According to /usr/share/doc/packages/rpm/manual/triggers and according
# to https://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets#Scriptlet_Ordering
# and http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering
# from the new package only "posttrans of new package" is run after "removal of old package"
# so that the new package must do the clean up as RPM posttrans scriptlet.
if systemctl --quiet is-enabled saptune.service 2>/dev/null; then
# Refresh still valid enabled systemd units and clean up possibly obsoleted systemd units:
# Enforce systemd to use the current unit file which is usually the unit file of the new package
# but also in case of custom units (that use other unit files) a "reenable" won't hurt because
# "reenable" does not implicitly stop a running service which is "the right thing" because
# a RPM package installation must not automatically disrupt (restart) a running service.
# Using "--force reenable" is essential to clean up possibly conflicting/broken symlinks.
# (without "|| :" build fails with "Failed to get D-Bus connection: No connection to service manager. posttrans script ... failed"):
systemctl --quiet --force reenable saptune.service 2>/dev/null || :
else
# Refresh still valid disabled systemd units and clean up possibly obsoleted systemd units:
# First using "--force reenable" is essential to clean up possibly conflicting/broken symlinks
# because there is no "--force disable" that would clean up possibly conflicting/broken symlinks
# see https://bugzilla.opensuse.org/show_bug.cgi?id=904215#c34
# so that first the unit has a clean state and then it is set back to disabled (as it was before).
# If a disabled systemd unit has become obsoleted, "systemctl --force reenable" will clean it up
# which means the unit gets removed and the subsequent "systemctl disable" will do nothing.
# (without "|| :" build fails with "Failed to get D-Bus connection: No connection to service manager. posttrans script ... failed"):
systemctl --quiet --force reenable saptune.service 2>/dev/null || :
systemctl --quiet disable saptune.service 2>/dev/null || :
fi
rm -f /run/saptune_during_pkg_inst
if [ -f /tmp/update_v1tov3_saptune_inst ]; then
rm -f /tmp/update_v1tov3_saptune_inst || :
# get back custom note definition files for BOBJ and/or ASE
# needed for migration, if customer had applied these notes
/usr/share/saptune/scripts/upd_helper v1tov2pt || :
else
# cleanup of old saptune v1 sysconfig files
# leftover from customer migration
for file in saptune-note-SUSE-GUIDE-01 saptune-note-1275776 saptune-note-SUSE-GUIDE-02 saptune-note-1557506; do
if [ -f /etc/sysconfig/${file} ]; then
rm -f /etc/sysconfig/${file}
fi
done
fi
if [ -f /tmp/update_sle12tosel15_saptune_inst ]; then
rm -f /tmp/update_sle12tosel15_saptune_inst || :
# check for SAP Note name changes between SLE12 and SLE15
/usr/share/saptune/scripts/upd_helper sle12to15pt || :
fi
if [ -f /tmp/update_saptune_staging_area ]; then
rm -f /tmp/update_saptune_staging_area || :
# handle staging area and DON'T touch the working area, needs to run
# after 'upd_helper sle12to15pt'
/usr/share/saptune/scripts/upd_helper staging || :
fi
if [ -f /run/saptune_is_active_in_tuned ]; then
# cleanup 'saptune with tuned is active' indicator
rm -f /run/saptune_is_active_in_tuned || :
# if saptune with tuned support was used/active (in v2 mode)
# stop and disable tuned service
# enable and start saptune service
# (jsc#SLE-10987 decision)
(systemctl stop tuned.service; systemctl disable tuned.service; systemctl enable saptune.service; systemctl start saptune.service) || :
fi
# bsc#1194688 - sometimes the tuned active profile is still 'saptune' even that
# the profile no longer exists. Try to clear.
[[ $(cat /etc/tuned/active_profile 2>/dev/null) == saptune ]] && (> /etc/tuned/active_profile) || :
exit 0 /bin/bash systemd-sysvcompat utf-8 ee95e1d6eb626119c29fd7ed2189553beb529e62ce26f01baf098a7c44deaa17 ? P 7zXZ
! t/!:] "k%{dC3 #D>VB}?d ;
A{]f1$Jw>짍FLzOx4={ZG5!֯.'"ټ 2uQѐ([xD)90@5/ei:}AʒsձUPx
y
;X"h+a] )k.1ĤRZJ_^l3xBlݛ*Bᵛ@*2&*W}R5VH| g.RKFA֒yӣK`cn. F ouy7-
o 7
%,CMU@6
oeb[/X|wĸ:G.8`F`A}B= p&zMOvjesLƱܛ@G6
"c_Dp__
xi w,d<9}rK̷p.3J- 9r$ &v1eB!"!5:]N葃CkT~0y61[?x#I LYru5( N` Ǐoџ)ܟ`PR"L<9m;`;BRNE s ^LI] -
nЗ;&VX_|b\S=jƿTz{Oo*=ws<ŏK /j |2⏬ k
1
LxXd ,Rbgjߔo)]a5+QdΧy \ᔱzosOV@5<GoaⲢP̚KO t|B~[: 'BJVHq׳V˵a
|
-NšCX# vJugK`gX9C(!
2=L6PZf=C斆 =OǍ:N5r5efҢn 65mFP,}u}W+ ͕qf(SfTCYr $M|\\z۵(4T?aT]ǰxvdiZdI#f')sn
+>m$J؇KO_ٔ뜆#YU=K " x7q 쾀ZCB|9M 5
ؔGDn K OhPҿ\R %RDʻ87N w9VnxY:n#k/ Hi<~ Zf^q""&?wb@l S?'ӻYpL8 #BE$Иb53nPМHXК:PiI\ ud^";2rnh diLVjwa ĺ"lb