[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#915536: marked as done (ITP: oomd -- userspace Out-Of-Memory (OOM) killer for)

Your message dated Wed, 16 Oct 2019 11:00:31 +0000
with message-id <E1iKh2d-000EXT-0g@fasolo.debian.org>
and subject line Bug#915536: fixed in oomd 0.1.0-1
has caused the Debian Bug report #915536,
regarding ITP: oomd -- userspace Out-Of-Memory (OOM) killer for
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
915536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915536
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist

* Package name    : oomd
  Version         : git HEAD
  Upstream Author : Dan Xu <dxu@apache.org>
* URL             : https://github.com/facebookincubator/oomd
* License         : GPL2
  Programming Lang: C++
  Description     : userspace Out-Of-Memory (OOM) killer for linux systems

oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd
then takes corrective action in userspace before an OOM occurs in kernel
space. Corrective action is configured via a flexible plugin system, in
which custom code can be written. By default, this involves killing
offending processes. This enables an unparalleled level of flexibility
where each workload can have custom protection rules. Furthermore, time
spent livedlocked in kernelspace is minimized.

--- End Message ---
--- Begin Message --- 
Source: oomd
Source-Version: 0.1.0-1

We believe that the bug you reported is fixed in the latest version of
oomd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 915536@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yangfl <mmyangfl@gmail.com> (supplier of updated oomd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 13 Aug 2019 14:59:22 +0800
Source: oomd
Binary: liboomd0 liboomd0-dbgsym oomd oomd-dbgsym
Architecture: source amd64
Version: 0.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl <mmyangfl@gmail.com>
Changed-By: Yangfl <mmyangfl@gmail.com>
Description:
 liboomd0   - userspace Out-Of-Memory (OOM) killer for Linux systems - library
 oomd       - userspace Out-Of-Memory (OOM) killer for Linux systems
Closes: 915536
Changes:
 oomd (0.1.0-1) unstable; urgency=medium
 .
   * Initial Release (closes: #915536)
Checksums-Sha1:
 b612fe0924fcbbadf1bf2a4c7302dbea67f17a91 2002 oomd_0.1.0-1.dsc
 29f74db21bb716871ed85d5ff9316e49c890a78f 66255 oomd_0.1.0.orig.tar.gz
 005bb5b65e1fc2ed38220dd0fa9113a135603241 13336 oomd_0.1.0-1.debian.tar.xz
 a5b9dc9d1257a8d1071a944137934e7ffab59440 2717656 liboomd0-dbgsym_0.1.0-1_amd64.deb
 76ff8781c066a8cd02237f52ce46eef9a844931d 123912 liboomd0_0.1.0-1_amd64.deb
 ddd28700a3dec6291339d52e202b493d3af33256 179880 oomd-dbgsym_0.1.0-1_amd64.deb
 d49df2ab88067794a0f21625827298e3c7a3b874 7188 oomd_0.1.0-1_amd64.buildinfo
 6c76451007c19d8fe0e21c0459ec449a527d94a8 19048 oomd_0.1.0-1_amd64.deb
Checksums-Sha256:
 2b42afa1763549081707e85cd59bab46dc91010a2fe1864b19ee6036c74ac8b4 2002 oomd_0.1.0-1.dsc
 422890af565683c62e2500698ce4cd4c956bb6068049ee0131a941f61298d85a 66255 oomd_0.1.0.orig.tar.gz
 8bb4934ccb71963385b3789b63449f1150ad20e846770b275c27e9f50b54d9e0 13336 oomd_0.1.0-1.debian.tar.xz
 d7c47bf080a1dd6e97bec2aa1d6e4159e720d9d92ce004d57408012b896c2633 2717656 liboomd0-dbgsym_0.1.0-1_amd64.deb
 7ad1123f2f0402c4db9e4ef0b88c0937079e23450297a632283d691a94b8180b 123912 liboomd0_0.1.0-1_amd64.deb
 1325c4d8c64a92188e5f30c726b4d7191d4cc8904f74467511a901474fe08161 179880 oomd-dbgsym_0.1.0-1_amd64.deb
 6791d56c924a3b009a62ccbfec6e42953f483afd3661a804a506f3e8b43f8217 7188 oomd_0.1.0-1_amd64.buildinfo
 5e081a0957b8d475f64eb6ee86f00154dc24893bfefaa86c91589f9ec33c0a0a 19048 oomd_0.1.0-1_amd64.deb
Files:
 58e5a4b96adb47b0075acba70b5ab955 2002 admin optional oomd_0.1.0-1.dsc
 abe3c2df99f53c8adc1290b7233d7732 66255 admin optional oomd_0.1.0.orig.tar.gz
 0b3310480f0efc5b5d72330b06b9690d 13336 admin optional oomd_0.1.0-1.debian.tar.xz
 8c9fe346611c88fc131d6e973f2c64d3 2717656 debug optional liboomd0-dbgsym_0.1.0-1_amd64.deb
 f01cb45b0e4d861b0c0571aef836b84a 123912 libs optional liboomd0_0.1.0-1_amd64.deb
 6f43bd57204420df545840d45940d5e5 179880 debug optional oomd-dbgsym_0.1.0-1_amd64.deb
 4adf959d33b1cbc3e05dd8871c09a186 7188 admin optional oomd_0.1.0-1_amd64.buildinfo
 3a89349e8e11f39fb095df6fc362cd0a 19048 admin optional oomd_0.1.0-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAl1/looPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhFBcP/34VDlpKwjjG51xQYqmsEcg338V3BT/KYOWu
PB+BkB7FvWkkFS7dlAjulwIWnWwv51uUq6S2PCQrN12DhgOlBSZ+fMjN29rZ/e3W
EMAPWXKd+ttMPqL/IWEDgdb97t2UOvULkNpm1kXewe/5rEKe6Cy6zL20jP3cx1l0
oN8dTwzDH+F1Vt94gP8EpKbwvOFjRQld7LFdU3XP6/n0N/eOvM4PVzg10OuQp9Pg
7udHBUrwfAMLRTcDkBBFYDWJG34ym/JDLtEPsxeeMVd3lbzMsQ7Azm+jrYIVg1eb
zZteGmumcE9Zquv9UweUh1gQnt/aSyL8eWdOYt35mK4XU6OBvchHo+D1271X4l0G
DJo7tUonzMxM5r/gtOahpKLi+Wp3Uq5iMX2k7jURvBhKi0ZogETVvGuFZeeDGEiN
neYGc5te7Vbzl7W5QHzXyT2JfUyeDp2hF+XGw8pUOV78e62z/Oh15c7YdhqbHNMu
//tnEqgPViOq79CneQpCxtI6KrIix6PD/lH7rKJgnmDX2RypSGa7iFmBxVCl9uuK
ImILbITmM4IlhDeP6LaKeFAyGt1Z8xSFonMgCySoKurJ+zvQacToUtEVf6lq2Qgv
MgHGGuBYlyDoriWn5gAi4NfUTp40fl+i+gOOKfR1Rc/ql8if1CaBSZGFnUL0Vkt9
/yq3DCOm
=en84
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: