Fedora-Cloud-33-20210523.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-33-20210522.0): ID: 892276 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/892276 ID: 892283 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/892283 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-32-20210523.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-32-20210522.0): ID: 892292 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/892292 ID: 892299 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/892299 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20210523.0 compose check report
No missing expected images. Failed openQA tests: 8/8 (x86_64) Old failures (same test failed in Fedora-Cloud-34-20210522.0): ID: 892302 Test: x86_64 Cloud_Base-qcow2-qcow2 base_services_start URL: https://openqa.fedoraproject.org/tests/892302 ID: 892303 Test: x86_64 Cloud_Base-qcow2-qcow2 base_reboot_unmount URL: https://openqa.fedoraproject.org/tests/892303 ID: 892304 Test: x86_64 Cloud_Base-qcow2-qcow2 base_service_manipulation URL: https://openqa.fedoraproject.org/tests/892304 ID: 892305 Test: x86_64 Cloud_Base-qcow2-qcow2 base_system_logging URL: https://openqa.fedoraproject.org/tests/892305 ID: 892306 Test: x86_64 Cloud_Base-qcow2-qcow2 base_selinux URL: https://openqa.fedoraproject.org/tests/892306 ID: 892307 Test: x86_64 Cloud_Base-qcow2-qcow2 base_update_cli URL: https://openqa.fedoraproject.org/tests/892307 ID: 892308 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/892308 ID: 892309 Test: x86_64 Cloud_Base-qcow2-qcow2 base_package_install_remove URL: https://openqa.fedoraproject.org/tests/892309 Soft failed openQA tests: 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20210522.0): ID: 892315 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/892315 Passed openQA tests: 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora rawhide compose report: 20210523.n.0 changes
OLD: Fedora-Rawhide-20210522.n.1 NEW: Fedora-Rawhide-20210523.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 2 Dropped packages:1 Upgraded packages: 32 Downgraded packages: 0 Size of added packages: 50.24 KiB Size of dropped packages:837.01 MiB Size of upgraded packages: 115.28 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 3.89 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: golang-github-lann-builder-0-0.1.20210521git47ae307.fc35 Summary: Fluent immutable builders for golang RPMs:golang-github-lann-builder-devel Size:14.52 KiB Package: golang-github-masterminds-squirrel-1.5.0-1.fc35 Summary: Fluent SQL generation for golang RPMs:golang-github-masterminds-squirrel-devel Size:35.71 KiB = DROPPED PACKAGES = Package: mld2p4-2.2.2-8.fc34 Summary: MultiLevel Domain Decomposition Parallel Preconditioners Package based on PSBLAS RPMs:mld2p4-common mld2p4-mpich mld2p4-mpich-devel mld2p4-openmpi mld2p4-openmpi-devel mld2p4-serial mld2p4-serial-devel Size:837.01 MiB = UPGRADED PACKAGES = Package: abcde-2.9.3-7.fc35 Old package: abcde-2.9.3-6.fc34 Summary: A Better CD Encoder RPMs: abcde Size: 122.43 KiB Size change: -824 B Changelog: * Sat May 22 2021 Dominik Mierzejewski - 2.9.3-7 - point to gnudb.org instead of the discontinued freedb.org (#1916974) Package: bottles-3.1.11-1.fc35 Old package: bottles-3.1.10-1.fc35 Summary: Easily manage Wine prefix in a new way RPMs: bottles Size: 173.00 KiB Size change: 545 B Changelog: * Sat May 22 2021 Artem Polishchuk - 3.1.11-1 - build(update): 3.1.11 Package: dummy-test-package-gloster-0-3803.fc35 Old package: dummy-test-package-gloster-0-3800.fc35 Summary: Dummy Test Package called Gloster RPMs: dummy-test-package-gloster Size: 235.46 KiB Size change: 129 B Changelog: * Sat May 22 2021 packagerbot - 0-3801 - rebuilt * Sat May 22 2021 packagerbot - 0-3802 - rebuilt * Sat May 22 2021 packagerbot - 0-3803 - rebuilt Package: golang-github-klauspost-compress-1.12.2-1.fc35 Old package: golang-github-klauspost-compress-1.12.1-1.fc35 Summary: Optimized compression packages RPMs: golang-github-klauspost-compress-devel Size: 279.34 KiB Size change: 1.36 KiB Changelog: * Sat May 22 2021 Dominik Mierzejewski - 1.12.1-1 - update to 1.12.2 (#1954254) - drop upstreamed patch Package: libedit-3.1-37.20210522cvs.fc35 Old package: libedit-3.1-36.20210419cvs.fc35 Summary: The NetBSD Editline library RPMs: libedit libedit-devel Size: 863.77 KiB Size change: -13.58 KiB Changelog: * Sat May 22 2021 Jerry James - 3.1-37.20210522cvs - New version (20210522-3.1) Package: minder-1.12.3-1.fc35 Old package: minder-1.12.2-1.fc35 Summary: Mind-mapping application RPMs: minder Size: 3.20 MiB Size change: -26.39 KiB Changelog: * Sat May 22 2021 Artem Polishchuk - 1.12.3-1 - build(update): 1.12.3 Package: mingw-boost-1.75.0-4.fc35 Old package: mingw-boost-1.75.0-3.fc34 Summary: MinGW Windows port of Boost C++ Libraries RPMs: mingw32-boost mingw32-boost-static mingw64-boost mingw64-boost-static Size: 33.03 MiB Size change: -159.16 KiB Changelog: * Sat May 22 2021 Sandro Mani - 1.75.0-4 - Rebuild (icu) Package: mingw-harfbuzz-2.8.1-2.fc35 Old package: mingw-harfbuzz-2.8.1-1.fc35 Summary: MinGW Windows Harfbuzz library RPMs: mingw32-harfbuzz mingw32-harfbuzz-static mingw64-harfbuzz mingw64-harfbuzz-static Size: 2.82 MiB Size change: -29.43 KiB Changelog: * Sat May 22 2021 Sandro Mani - 2.8.1-2 - Rebuild (icu) Package: mingw-icu-69.1-1.fc35 Old package: mingw-icu-67.1-3.fc34 Summary: MinGW compilation of International Components for Unicode Tools RPMs: mingw32-icu mingw64-icu Size: 23.57 MiB Size change: 1.91 MiB Changelog: * Sat May 22 2021 Sandro Mani - 69.1-1 - Update to 69.1 Package: mingw-qt5-qtwebkit-5.212.0-0.14.alpha4.fc35 Old package: mingw-qt5-qtwebkit-5.212.0-0.13.alpha4.fc34 Summary: Qt5 for Windows - QtWebKit component RPMs: mingw32-qt5-qtwebkit mingw64-qt5-qtwebkit Size: 31.47 MiB Size change: -81.54 KiB Changelog: * Sat May 22 2021 Sandro Mani - 5.212.0-0.14.alpha4 - Rebuild (icu) Package: mingw-sword-1.9.0-3.fc35 Old package: mingw-sword-1.9.0-2.fc34 Summary: MinGW build of a cross-platform scripture text library RPMs: mingw32-sword mingw64-sword Size: 2.10 MiB Size change: 19.21 KiB Changelog: * Sat May 22 2021 Sandro Mani - 1.9.0-3 - Rebuild (icu) Package: mpfr-4.1.0-7.fc35 Old package: mpfr-4.1.0-6.fc35 Summary: C library for multiple-precision floating-point
Earlyoom and systemd-oomd together
Hi, I've upgraded from F33 to F34 using dnf plugin and I've found that both systemd-oomd and earlyoom service are running: systemctl is-active earlyoom.service systemd-oomd.service active active and: systemctl is-active earlyoom.service systemd-oomd.service active active Is this behaviour expected? Thanks in advance -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Earlyoom and systemd-oomd together
On Sun, May 23, 2021 at 9:59 AM Sergio Belkin wrote: > > Hi, > I've upgraded from F33 to F34 using dnf plugin and I've found that both > systemd-oomd and earlyoom service are running: > > systemctl is-active earlyoom.service systemd-oomd.service > active > active > > and: > > systemctl is-active earlyoom.service systemd-oomd.service > active > active > > Is this behaviour expected? > No. The earlyoom service is supposed to get disabled on upgrade to Fedora Linux 34. This is a bug and needs to be fixed. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Earlyoom and systemd-oomd together
El dom, 23 may 2021 a las 11:01, Neal Gompa () escribió: > On Sun, May 23, 2021 at 9:59 AM Sergio Belkin wrote: > > > > Hi, > > I've upgraded from F33 to F34 using dnf plugin and I've found that both > systemd-oomd and earlyoom service are running: > > > > systemctl is-active earlyoom.service systemd-oomd.service > > active > > active > > > > and: > > > > systemctl is-active earlyoom.service systemd-oomd.service > > active > > active > > > > Is this behaviour expected? > > > > No. The earlyoom service is supposed to get disabled on upgrade to > Fedora Linux 34. This is a bug and needs to be fixed. > > > I suppposed it, thanks Neal! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Rawhide-20210523.n.0 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 7 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 21/194 (x86_64), 18/133 (aarch64) New failures (same test not failed in Fedora-Rawhide-20210522.n.1): ID: 892399 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/892399 ID: 892454 Test: aarch64 Server-dvd-iso install_vnc_server@uefi URL: https://openqa.fedoraproject.org/tests/892454 ID: 892469 Test: aarch64 Server-dvd-iso install_vnc_client@uefi URL: https://openqa.fedoraproject.org/tests/892469 ID: 892483 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/892483 ID: 892521 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/892521 ID: 892629 Test: aarch64 universal install_kickstart_hdd@uefi URL: https://openqa.fedoraproject.org/tests/892629 Old failures (same test failed in Fedora-Rawhide-20210522.n.1): ID: 892335 Test: x86_64 Server-dvd-iso server_remote_logging_server URL: https://openqa.fedoraproject.org/tests/892335 ID: 892338 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/892338 ID: 892344 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/892344 ID: 892369 Test: x86_64 Server-dvd-iso server_remote_logging_client URL: https://openqa.fedoraproject.org/tests/892369 ID: 892375 Test: x86_64 Everything-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/892375 ID: 892376 Test: x86_64 Everything-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/892376 ID: 892387 Test: x86_64 Workstation-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/892387 ID: 892390 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/892390 ID: 892403 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/892403 ID: 892412 Test: x86_64 KDE-live-iso desktop_terminal **GATING** URL: https://openqa.fedoraproject.org/tests/892412 ID: 892414 Test: x86_64 KDE-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/892414 ID: 892459 Test: aarch64 Server-dvd-iso install_blivet_resize_lvm@uefi URL: https://openqa.fedoraproject.org/tests/892459 ID: 892477 Test: aarch64 Server-dvd-iso server_role_deploy_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/892477 ID: 892479 Test: aarch64 Server-dvd-iso server_remote_logging_server@uefi URL: https://openqa.fedoraproject.org/tests/892479 ID: 892485 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi URL: https://openqa.fedoraproject.org/tests/892485 ID: 892490 Test: aarch64 Server-dvd-iso server_remote_logging_client@uefi URL: https://openqa.fedoraproject.org/tests/892490 ID: 892501 Test: aarch64 Workstation-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/892501 ID: 892533 Test: x86_64 universal install_repository_http_variation **GATING** URL: https://openqa.fedoraproject.org/tests/892533 ID: 892547 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/892547 ID: 892551 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/892551 ID: 892565 Test: x86_64 universal install_repository_http_graphical **GATING** URL: https://openqa.fedoraproject.org/tests/892565 ID: 892570 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/892570 ID: 892574 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/892574 ID: 892586 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/892586 ID: 892588 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/892588 ID: 892589 Test: x86_64 universal install_mirrorlist_graphical **GATING** URL: https://openqa.fedoraproject.org/tests/892589 ID: 892608 Test: aarch64 universal install_cyrillic_language@uefi URL: https://openqa.fedoraproject.org/tests/892608 ID: 892609 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/892609 ID: 892615 Test: aarch64 universal install_repository_http_graphical@uefi URL: https://openqa.fedoraproject.org/tests/892615 ID: 892620 Test: aarch64 universal install_repository_http_variation@uefi URL: https://openqa.fedoraproject.org/tests/892620 ID: 892624 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/892624 ID: 892634 Test: aarch64 universal in
Re: HEADS UP: icu 69 coming to rawhide
On Wed, 2021-05-19 at 14:59 +0100, Pete Walter wrote: > I am in the process of updating icu from 67.1 to 69.1 in rawhide. This comes > with a soname bump, but as usual, I'm including a compat package providing > the old soname to not break the world while the rebuilds are in progress, so > no rawhide breakage is expected. I'll work on the rebuilds over the weekend. Shouldn't this be done in a side tag? -- Yaakov Selkowitz Senior Software Engineer - Platform Enablement Red Hat, Inc. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Is really systemd-oomd enforced?
Hi,
I was reading the systemd-oomd documentation and it says:
«More precisely, only cgroups with memory.oom.group set to 1 and leaf
cgroup nodes are eligible candidates.»
(https://www.freedesktop.org/software/systemd/man/systemd-oomd.html)
However I haven't found any "memory.oom.group" file set to 1:
sudo find /sys -name "memory.oom.group" -exec grep -v '^0$' '{}' \; | wc -l
0
So, Should I set memory.oom.group to 1?
Thanks in advance?
--
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Is really systemd-oomd enforced?
On Sun, May 23, 2021 at 11:54 AM Sergio Belkin wrote:
>
> Hi,
> I was reading the systemd-oomd documentation and it says:
> «More precisely, only cgroups with memory.oom.group set to 1 and leaf cgroup
> nodes are eligible candidates.»
> (https://www.freedesktop.org/software/systemd/man/systemd-oomd.html)
>
> However I haven't found any "memory.oom.group" file set to 1:
>
> sudo find /sys -name "memory.oom.group" -exec grep -v '^0$' '{}' \; | wc -l
> 0
>
> So, Should I set memory.oom.group to 1?
>
Do you have systemd-oomd-defaults installed? That's where the oomd
configuration is stored.
--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Is really systemd-oomd enforced?
El dom, 23 may 2021 a las 12:58, Neal Gompa () escribió:
> On Sun, May 23, 2021 at 11:54 AM Sergio Belkin wrote:
> >
> > Hi,
> > I was reading the systemd-oomd documentation and it says:
> > «More precisely, only cgroups with memory.oom.group set to 1 and leaf
> cgroup nodes are eligible candidates.»
> > (https://www.freedesktop.org/software/systemd/man/systemd-oomd.html)
> >
> > However I haven't found any "memory.oom.group" file set to 1:
> >
> > sudo find /sys -name "memory.oom.group" -exec grep -v '^0$' '{}' \; |
> wc -l
> > 0
> >
> > So, Should I set memory.oom.group to 1?
> >
>
> Do you have systemd-oomd-defaults installed? That's where the oomd
> configuration is stored.
>
>
>
> --
>
> Hi Neal
rpm -qil systemd-oomd-defaults
Name: systemd-oomd-defaults
Version : 248.3
Release : 1.fc34
Architecture: x86_64
Install Date: jue 20 may 2021 06:06:11
Group : Unspecified
Size: 145
License : LGPLv2+
Signature : RSA/SHA256, sáb 15 may 2021 17:50:23, Key ID 1161ae6945719a39
Source RPM : systemd-248.3-1.fc34.src.rpm
Build Date : sáb 15 may 2021 14:10:24
Build Host : buildvm-x86-09.iad2.fedoraproject.org
Packager: Fedora Project
Vendor : Fedora Project
URL : https://www.freedesktop.org/wiki/Software/systemd
Bug URL : https://bugz.fedoraproject.org/systemd
Summary : Configuration files for systemd-oomd
Description :
A set of drop-in files for systemd units to enable action from systemd-oomd,
a userspace out-of-memory (OOM) killer.
/usr/lib/systemd/oomd.conf.d
/usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf
/usr/lib/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
/usr/lib/systemd/system/user@.service.d/10-oomd-user-service-defaults.conf
And:
cat /usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf
/usr/lib/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
/usr/lib/systemd/system/user@.service.d/10-oomd-user-service-defaults.conf
[OOM]
DefaultMemoryPressureDurationSec=20s
[Slice]
ManagedOOMSwap=kill
[Service]
ManagedOOMMemoryPressure=kill
ManagedOOMMemoryPressureLimit=50%
Just in case:
systemd-analyze cat-config /etc/systemd/oomd.conf | egrep -v '^$|#'
[OOM]
[OOM]
DefaultMemoryPressureDurationSec=20s
Still it's not clear for me if systemd-oomd is really enforced :)
--
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Is really systemd-oomd enforced?
On Sun, May 23 2021 at 11:57:03 AM -0400, Neal Gompa wrote: Do you have systemd-oomd-defaults installed? That's where the oomd configuration is stored. Hm, I did not have this installed after upgrading to F34, and I still had earlyoom installed too. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: sudo dnf remove gtk3
Okay, so I asked here: https://discourse.gnome.org/t/does-gnome-shell-use-gtk3-or-gtk4/6530 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Earlyoom and systemd-oomd together
On 23.05.2021 16:00, Neal Gompa wrote: This is a bug and needs to be fixed. This is not an earlyoom's bug: https://src.fedoraproject.org/rpms/earlyoom/blob/rawhide/f/earlyoom.spec#_44 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is really systemd-oomd enforced?
On 23.05.2021 18:38, Michael Catanzaro wrote: I still had earlyoom installed too. This is intended. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is really systemd-oomd enforced?
El dom, 23 may 2021 a las 13:10, Sergio Belkin ()
escribió:
>
>
> El dom, 23 may 2021 a las 12:58, Neal Gompa ()
> escribió:
>
>> On Sun, May 23, 2021 at 11:54 AM Sergio Belkin wrote:
>> >
>> > Hi,
>> > I was reading the systemd-oomd documentation and it says:
>> > «More precisely, only cgroups with memory.oom.group set to 1 and leaf
>> cgroup nodes are eligible candidates.»
>> > (https://www.freedesktop.org/software/systemd/man/systemd-oomd.html)
>> >
>> > However I haven't found any "memory.oom.group" file set to 1:
>> >
>> > sudo find /sys -name "memory.oom.group" -exec grep -v '^0$' '{}' \; |
>> wc -l
>> > 0
>> >
>> > So, Should I set memory.oom.group to 1?
>> >
>>
>> Do you have systemd-oomd-defaults installed? That's where the oomd
>> configuration is stored.
>>
>>
>>
>> --
>>
>> Hi Neal
>
> rpm -qil systemd-oomd-defaults
> Name: systemd-oomd-defaults
> Version : 248.3
> Release : 1.fc34
> Architecture: x86_64
> Install Date: jue 20 may 2021 06:06:11
> Group : Unspecified
> Size: 145
> License : LGPLv2+
> Signature : RSA/SHA256, sáb 15 may 2021 17:50:23, Key ID 1161ae6945719a39
> Source RPM : systemd-248.3-1.fc34.src.rpm
> Build Date : sáb 15 may 2021 14:10:24
> Build Host : buildvm-x86-09.iad2.fedoraproject.org
> Packager: Fedora Project
> Vendor : Fedora Project
> URL : https://www.freedesktop.org/wiki/Software/systemd
> Bug URL : https://bugz.fedoraproject.org/systemd
> Summary : Configuration files for systemd-oomd
> Description :
> A set of drop-in files for systemd units to enable action from
> systemd-oomd,
> a userspace out-of-memory (OOM) killer.
> /usr/lib/systemd/oomd.conf.d
> /usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf
> /usr/lib/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
> /usr/lib/systemd/system/user@.service.d/10-oomd-user-service-defaults.conf
>
> And:
>
> cat /usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf
> /usr/lib/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
> /usr/lib/systemd/system/user@.service.d/10-oomd-user-service-defaults.conf
> [OOM]
> DefaultMemoryPressureDurationSec=20s
> [Slice]
> ManagedOOMSwap=kill
> [Service]
> ManagedOOMMemoryPressure=kill
> ManagedOOMMemoryPressureLimit=50%
>
> Just in case:
> systemd-analyze cat-config /etc/systemd/oomd.conf | egrep -v '^$|#'
> [OOM]
> [OOM]
> DefaultMemoryPressureDurationSec=20s
>
> Still it's not clear for me if systemd-oomd is really enforced :)
>
> --
> --
> Sergio Belkin
> LPIC-2 Certified - http://www.lpi.org
>
I was looking at https://testdays.fedoraproject.org/events/105
Swap Based Killing worked for but "Memory Pressure Based Killing" didn't
(stress-ng is not killed by systemd-oomd as is in
https://fedoraproject.org/wiki/QA:Testcase_Memory_Pressure_Based_Killing#How_to_test
):
may 23 13:46:34 munster.belkin.home kernel: Timer invoked oom-killer:
gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
This is oomctl output:
Dry Run: no
Swap Used Limit: 90.00%
Default Memory Pressure Limit: 60.00%
Default Memory Pressure Duration: 20s
System Context:
Swap: Used: 6.0G Total: 7.9G
Swap Monitored CGroups:
Memory Pressure Monitored CGroups:
Path: /user.slice/user-1000.slice/user@1000.service
Memory Pressure Limit: 50.00%
Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 1.83 Total: 51s
Current Memory Usage: 5.9G
Memory Min: 0B
Any ideas?
--
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Earlyoom and systemd-oomd together
On Sun, May 23, 2021 at 12:45 PM Vitaly Zaitsev via devel wrote: > > On 23.05.2021 16:00, Neal Gompa wrote: > > This is a bug and needs to be fixed. > > This is not an earlyoom's bug: > > https://src.fedoraproject.org/rpms/earlyoom/blob/rawhide/f/earlyoom.spec#_44 > Actually, it is. That trigger is wrong: https://src.fedoraproject.org/rpms/earlyoom/blob/rawhide/f/earlyoom.spec#_41 It should be instead: %triggerun -- fedora-release-common < 34 -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Earlyoom and systemd-oomd together
On 23.05.2021 19:05, Neal Gompa wrote: Actually, it is. That trigger is wrong: https://src.fedoraproject.org/rpms/earlyoom/pull-request/3 It should be instead: %triggerun -- fedora-release-common < 34 Should I fix this? -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Earlyoom and systemd-oomd together
On 23.05.2021 19:05, Neal Gompa wrote: Actually, it is. That trigger is wrong: It should work fine. Version in Fedora 33: earlyoom-1.6.2-1.fc33. Version in Fedora 34: earlyoom-1.6.2-3.fc34. The trigger is: earlyoom < 1.6.2-3 It will be automatically executed on F34 upgrade. I tested it in VM. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Earlyoom and systemd-oomd together
What do you get for: sudo systemctl status earlyoom.service I see: Loaded: loaded (/usr/lib/systemd/system/earlyoom.service; disabled; vendor preset: disabled) Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: When is pappl going to be good enough to replace cups?
Hi Vitaly, Openprinting community (which I am a part of the community) plans to have printer applications for printer drivers shipped in Ubuntu implemented during Google Summer of Code [1] by multiple students. foo2zjs is in Ubuntu too, so there's a plan to implement a printer application for it. However, if you don't want to rely/wait for GSoC results, one student from Google Season of Docs last year created a documentation for implementing printer applications [2][3], so you can learn more about how a printer application works and you're welcome to join our OpenPrinting community and help us implementing the foo2zjs printer application. [1] https://wiki.linuxfoundation.org/gsoc/google-summer-code-2021-openprinting-projects [2] https://openprinting.github.io/documentation/01-printer-application/ [3] https://openprinting.github.io/documentation/02-designing-printer-drivers/ On 5/21/21 10:30 AM, Vitaly Zaitsev via devel wrote: > On 21.05.2021 08:24, Zdenek Dohnal wrote: >> If your printer is network printer released approx. 2010 and later or >> USB printer released approx. 2015 and later (tips how to find out if >> your device supports driverless printing here [4]), you don't even >> need to install your printer anymore, not mention using a printer >> driver (or future printer applications). > > What about "win-printers" like HP LajerJet P1102w? > > Currently I maintain and use foo2zjs to use them without the > proprietary "plugins" from hplip. > -- Zdenek Dohnal Software Engineer Red Hat Czech - Brno TPB-C OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: When is pappl going to be good enough to replace cups?
On 5/22/21 12:17 AM, Kevin Kofler via devel wrote: > Zdenek Dohnal wrote: >> It is a library for printer applications [1], not a substitute for CUPS. >> CUPS is still present and is going to be. >> >> There will be more printer applications coming into Fedora >> (ps-printer-app f.e.) and one already is (lprint). >> >> >> The purpose of the library is have a way how to implement a support for >> devices which don't support IPP Everywhere [2] or its derivations >> (Airprint, Mopria, Google cloud print) or IPP over USB[3], so they can >> be seen by CUPS once we remove printer driver support. Hi Kevin, > I really don't see how the switch from drivers to printer applications is an > improvement. Printer applications started as a transition technology - a way how to support older printers once CUPS removes printer driver support - so for now they are here for backward compatibility. Except for Gutenprint, I'm not aware of any printer driver provider which plans to provide more specific options with a printer application. They seem to be okay with AirPrint. So printer application will be needed only for older (<2010) printer models in most cases. > All the existing drivers have to be ported to the new interface > to essentially emulate the IPP protocol. And now, instead of being able to > configure printer options through the existing graphical CUPS frontends (or > just set them temporarily in the individual application, which most > applications support nowadays), you end up with a CLI as in the old lpr > days, e.g.: > https://www.msweet.org/lprint/lprint.html#printing-options > https://www.msweet.org/lprint/lprint.html#setting-default-options > or at best, a GUI provided by the printer application in some arbitrary > toolkit, which will likely be GTK for Gutenprint (forcing KDE Plasma users > to use a GTK application to configure their printer) and Qt for HPLIP > (forcing GNOME users to use a Qt application to configure their printer). > Instead of a standardized interface to configure printer options, every > printer application now has to reinvent its own one. AFAIK PAPPL (and even the old lprint which I packaged into Fedora last year, but his web interface is going to substituted by PAPPL web ui in the next release) provides a default web interface which you can use for configuring printer options. > > From the end user perspective, the new approach brings only disadvantages. Since PAPPL provides web ui and CLI, which you can use for configuring your device, IMHO it is not much different from what CUPS provides right now. > From the driver developer perspective, it means a lot of porting work. It depends on which devices he creates drivers for - if the device supports Airprint, he can choose to let Airprint to support the printer and no printer application is needed. >From my daily work, I see people often use drivers because they are used to using it and don't know they don't need to use it. For older devices, yes, there needs to be a printer application to be able to use the device with CUPS in the future, but OpenPrinting plans to implement printer applications for widely known printer driver packages during GSoC [1] and provides a documentation for driver developers who wants to implement their printer application faster[2][3]. > The > only ones who will benefit are the CUPS developers, who will have > successfully outsourced their work to other projects that now have to do > their work for them. CUPS developers (PWG+Openprinting) decided to remove deprecated functionality (which has big issues regarding security and distribution) in the future in favor of standardized, less hardware dependent solution, which is supported by 98% of printers released since 2010. The functionality has been deprecated for 11 years and still be only deprecated (not removed) until there is a coverage for older devices by printer applications and have some tools for installing older printers via printer applications. CUPS developers came up with printer application design for older device users, so they don't have to buy a new device, created first three printer applications - ippeveprinter (shipped in CUPS itself, under cups-printerapp subpackage in Fedora), lprint (support for label printers) and ps-printer-app (which covers postscript printers) -, plans to implement printer applications for other widely packaged printer drivers and publicly provides a documentation how to create printer applications for corner use cases. [1] https://wiki.linuxfoundation.org/gsoc/google-summer-code-2021-openprinting-projects [2] https://openprinting.github.io/documentation/01-printer-application/ [3] https://openprinting.github.io/documentation/02-designing-printer-drivers/ > > Kevin Kofler > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs
