vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 503409dcc926df9f0c299231e177aef26c7ce08f
Author: yangfl <yangfl@users.noreply.github.com>
Date: Mon Jan 4 21:44:58 2021 +0800
debian: update to 1.6.2
commit ea80426df057558d04733291a16f57e38395e6c8
Merge: 0c4b78c 445bda1
Author: yangfl <yangfl@users.noreply.github.com>
Date: Mon Jan 4 21:43:50 2021 +0800
Merge tag 'v1.6.2'
earlyoom v1.6.2
Closes https://github.com/rfjakob/earlyoom/issues/225
commit 0c4b78c70881647c7b0c67a260eedb38fcecfd7c
Author: yangfl <yangfl@users.noreply.github.com>
Date: Mon May 4 15:57:05 2020 +0800
debian: update to 1.6
commit 7435806a011a4ea9d57befa95e1ad5a6001ef36c
Merge: 43d3048 924f7b2
Author: yangfl <yangfl@users.noreply.github.com>
Date: Mon May 4 15:48:28 2020 +0800
Merge tag 'v1.6'
earlyoom v1.6
commit 43d30482642c5476b818f68be0c641d1f39155bc
Author: yangfl <yangfl@users.noreply.github.com>
Date: Wed Apr 8 12:30:37 2020 +0800
debian: fix FTBFS on 32-bit archs
commit aac133e9aaa27b8bd328f5dde0d9bf5624eb773f
Author: yangfl <yangfl@users.noreply.github.com>
Date: Thu Mar 12 18:19:15 2020 +0800
debian: update to 1.5
commit eb43dcdc54e5693df7c5dfacd8880653b46cc586
Merge: 709bda7 245e467
Author: yangfl <yangfl@users.noreply.github.com>
Date: Sat Mar 28 11:27:34 2020 +0800
Merge tag 'v1.5'
earlyoom v1.5
commit 709bda7e62eedb0db1401da9857d68b1167b4416
Author: yangfl <yangfl@users.noreply.github.com>
Date: Tue Mar 10 12:23:52 2020 +0800
debian: fix FTBFS
commit a1266f0323ee06656805be98d37ad6e5a3dd203b
Author: yangfl <yangfl@users.noreply.github.com>
Date: Tue Mar 3 17:20:07 2020 +0800
debian: update to 1.4
commit 1f262f524d489bc9a240834589b500679ae884a0
Merge: 7934717 8f4eaf7
Author: yangfl <yangfl@users.noreply.github.com>
Date: Tue Mar 3 16:52:27 2020 +0800
Merge tag 'v1.4'
earlyoom v1.4
commit 7934717a1ef8037d1fab59133677e52cb8a778ba
Author: yangfl <yangfl@users.noreply.github.com>
Date: Tue Jul 9 10:10:37 2019 +0800
debian: fix tests error
commit eb0b0a3c01b4cbb3a2d5cd0cf24a7d46ee846652
Author: Boyuan Yang <byang@debian.org>
Date: Sun Jul 7 12:05:25 2019 -0400
Bump Standards-Version to 4.4.0.
commit f05265b88fc79dab8a56fbf3bd7520bddac3a8cd
Author: yangfl <yangfl@users.noreply.github.com>
Date: Thu Jul 4 17:16:42 2019 +0800
debian: update to 1.3
commit 5fff6ac62c7d86e6a01629978f0b129a7a177d2f
Merge: 5b1666f b785b32
Author: yangfl <yangfl@users.noreply.github.com>
Date: Thu Jul 4 16:29:28 2019 +0800
Merge tag 'v1.3'
earlyoom v1.3
commit b785b32c6722e249386283eb6dc27ca714e0d6b1
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun May 26 17:37:29 2019 +0200
Update changelog for v1.3
commit b0b6e78e36e64467f0375a36bcee9b691e03658e
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun May 26 17:37:22 2019 +0200
make format
commit fe42d76700540904f12108e3881c58ff0c5b16ba
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun May 5 23:04:49 2019 +0200
Add contrib/oomstat
Shows available memory and /proc/pressure values.
$ go build && ./oomstat
Time MemAvail SwapFree Some Full
0.0 22368 57 0 0
0.1 22368 57 0 0
0.2 22368 57 0 0
0.3 22368 57 0 0
[...]
commit ba444e2391d87c480b4b12712e82e5ff8ee0aa87
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Mon Apr 29 20:35:30 2019 +0200
Enhance debug output during kill_wait
https://github.com/rfjakob/earlyoom/issues/131
selecting victim took 6.900 ms
sending SIGTERM to process 2828 "membomb": badness 754, VmRSS 18044 MiB
mem avail: 2493 of 23952 MiB (10 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 2250 of 23952 MiB ( 9 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 2008 of 23952 MiB ( 8 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 1766 of 23952 MiB ( 7 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 1524 of 23952 MiB ( 6 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 1283 of 23952 MiB ( 5 %), swap free: 0 of 0 MiB ( 0 %)
escalating to SIGKILL after 0.5 seconds
process state: R
mem avail: 2607 of 23952 MiB (10 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 4349 of 23952 MiB (18 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 6471 of 23952 MiB (27 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 8867 of 23952 MiB (37 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 11325 of 23952 MiB (47 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 13806 of 23952 MiB (57 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 16295 of 23952 MiB (68 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 18783 of 23952 MiB (78 %), swap free: 0 of 0 MiB ( 0 %)
process state: R
mem avail: 20574 of 23952 MiB (85 %), swap free: 0 of 0 MiB ( 0 %)
process exited after 1.4 seconds
commit 8887f63a1b9382e66601e0052fa9646e053d2d49
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Apr 28 21:15:00 2019 +0200
Fix display of truncated utf8 names
Fixes https://github.com/rfjakob/earlyoom/issues/110
commit 4c5eefc288a96d690beed997a78a204ea143a4f6
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Apr 28 20:58:37 2019 +0200
Rename go files to clearer names
renamed: tests/c.go -> tests/c_wrappers.go
renamed: tests/c_unit_test.go -> tests/unit_test.go
commit f89701d84bbae3146b6c4a6d62f6bec45e298df0
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Apr 28 20:57:33 2019 +0200
Add fix_truncated_utf8
https://github.com/rfjakob/earlyoom/issues/110
commit 95a6bdbb47fc3414714a6facbf93ac136cea5fe4
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Apr 28 15:46:23 2019 +0200
kill_wait: escalate to SIGKILL *within* the wait loop
Also, move the usleep to *after* the memory check for
faster reaction time.
We used to return from the kill_wait loop when we drop
below the SIGKILL limits and would immediately be called
again. This means a new victim would be selected, which
may be the wrong one because the original victim is in
the process of being cleaned up, did not release the memory
yet, but does not have a VmRSS value in /proc anymore.
commit 8c6fdb183fe7a9d0073db8d63b0a06e0d5abce4a
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Apr 28 15:45:07 2019 +0200
Use human-readable signal names SIGTERM / SIGKILL in messages
Before:
killing process 12588 "membomb" with signal 15: badness 328, VmRSS 7858 MiB
After:
sending SIGTERM to process 12070 "membomb": badness 328, VmRSS 7853 MiB
commit 07a9ccea3ae64febd90f0a9657cc7d9723231bf8
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 23:29:50 2019 +0200
kill_wait: don't abort wait when we already sent SIGKILL
commit 31d08d446a74987399d3d17dc97cd8cf49b31a54
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 19:22:13 2019 +0200
make format
commit 614055e51dce9d68ffabe079d940fae678b7c239
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 19:19:22 2019 +0200
kill_wait: abort wait if we drop below SIGKILL limit
This prevents programs that block SIGTERM from incapacitating
us.
https://github.com/rfjakob/earlyoom/issues/121
commit b828eb69094f12b1e02216cc02ec106d78480c3a
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 19:16:17 2019 +0200
membomb: block SIGTERM
Make it as worst-case as possible.
commit 8bfd167b7fdd9dd68235fe94463f337801a7b37c
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 18:30:09 2019 +0200
kill_wait: fix timeout error reporting
Used to look like this:
killing process 27366 "bash" with signal 15: badness 539, VmRSS 7464 MiB
timeout waiting for pid 27366 after signal 15
kill failed: Success. Sleeping 1 second
https://github.com/rfjakob/earlyoom/issues/121
commit 3edd3407c49d7603f8652374faa2ed938ff76638
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 18:25:56 2019 +0200
Read process name from /proc/[pid]/comm instead of stat
Gets rid of one fscanf and problems with ")".
commit c1bcbc7ac3c6324904c147a78f1a189c7d9f2c2b
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 17:29:16 2019 +0200
Fix gcc -O2 / -O3 truncation warnings
Fixes https://github.com/rfjakob/earlyoom/issues/127
Warnings were:
cc -Wall -Wextra -DVERSION=\"v1.3-rc1-dirty\" -g -fstack-protector-all -std=gnu99 -O3 -o earlyoom meminfo.c kill.c globals.c msg.c main.c sanitize.c
kill.c: In function ‘kill_largest_process’:
kill.c:53:40: warning: ‘%s’ directive output may be truncated writing up to 5095 bytes into a region of size 599 [-Wformat-truncation=]
snprintf(notif, sizeof(notif), "%s %s", notif_command, notif_args);
^~
kill.c:215:42:
maybe_notify(args.notif_command, notif_args);
~~~~~~~~~~
kill.c:53:5: note: ‘snprintf’ output 2 or more bytes (assuming 5097) into a destination of size 600
snprintf(notif, sizeof(notif), "%s %s", notif_command, notif_args);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
kill.c:178:13: warning: ‘strncpy’ output may be truncated copying 4095 bytes from a string of length 4095 [-Wstringop-truncation]
strncpy(victim_name, name, sizeof(victim_name) - 1);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
kill.c:172:13: warning: ‘strncpy’ output may be truncated copying 4095 bytes from a string of length 4095 [-Wstringop-truncation]
strncpy(victim_name, name, sizeof(victim_name) - 1);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
commit 61ef7c0ad35fd397b993a3555ffff42dda1a0b78
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 16:36:18 2019 +0200
Suppress "fopen 22275/oom_score failed" messages
These appear on every startup via systemd and are just useless
noise.
Apr 27 16:31:15 brikett earlyoom[22283]: fopen 22275/oom_score failed: No such file or directory
Apr 27 16:31:15 brikett earlyoom[22283]: fopen 22281/oom_score failed: No such file or directory
Apr 27 16:31:15 brikett earlyoom[22283]: fopen 22282/oom_score failed: No such file or directory
commit fe9bbfbbac399620812ba5ee52de98176ecb0d55
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 16:32:08 2019 +0200
Makefile: set SELinux label for systemd unit file
Otherwise systemd cannot load the file on Fedora 29.
commit 6b72e8a9b17dcd31e067319b1cdab58bfe1bc250
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 16:23:52 2019 +0200
Update changelog
commit 4c68c6a982befbde3dccb853c6a3a572d0e60e42
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 16:20:26 2019 +0200
Try to make output a little nicer
Also, rename userspace_kill() -> kill_largest_process().
commit ab1dd510c79af761b8a149cf3444cffd3be6c6d8
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 15:32:32 2019 +0200
wait for actual process exit after sending signal
https://github.com/rfjakob/earlyoom/issues/121
commit f7324597f9e252b686ab9f0f12205942751bb25b
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 14:12:52 2019 +0200
Drop args.procdir
Having the file handle to /proc does not make a lot of sense, as
get_process_stats() does not use it, and main() guarantees that
our CWD is /proc.
commit c374776ab455b3a6e97d3d15f8389efe78aa2cea
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 14:05:51 2019 +0200
contrib: add mon.sh
For analyzing https://github.com/rfjakob/earlyoom/issues/121
commit 41cb5f38184b34063d01d4aa96495e749efe68e3
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Apr 27 13:49:09 2019 +0200
contrib: add zombie
Simple toy program that creates a zombie process.
commit 390be04cdb3bc395001d938729d8fd70d16af50e
Author: gvtek0 <46519126+gvtek0@users.noreply.github.com>
Date: Thu Apr 18 23:34:15 2019 -0700
Me being pedantic about some spelling/words (#126)
Noticed a small spelling error, s/what/that
s/to/up (I think in line 22, otherwise was "to to 10")
Line 144 "on" removed, not sure but maybe was supposed to be "only" but read more like it wasn't needed.
commit 1fa9faabc2d5e6869c115691da87723ea6a1eaa0
Author: yangfl <yangfl@users.noreply.github.com>
Date: Sun Mar 10 14:48:18 2019 +0800
wrap help message at 80 characters
commit 77ea74a36565890ead0f1ea1f7904e5bb4cda3cc
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Mon Feb 25 17:59:17 2019 +0900
update readme: electron oom_score_adj
commit 2391f96761ca6041adcc7a4972d1a4be2136d626
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Wed Feb 20 19:43:48 2019 +0100
help text: note that BOTH memory and swap must be below min
fixes https://github.com/rfjakob/earlyoom/issues/118
commit 15fd5a11f9b830578dbe18f592bdb2bf94ddb8e8
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Mon Jan 14 18:24:52 2019 +0900
Update README.md
commit 3ac870f9aea04ee35ba5963fedcb111048c34eb1
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Wed Jan 23 02:06:07 2019 +0900
fix notify helper: add DISPLAY
commit ddfb5f1c5212f061be5e34212d2b330fd08e5bfc
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Wed Jan 23 00:04:10 2019 +0900
fix notify helper
fix env, remove DISPLAY
commit a6a84b7a14e5d2006cbadc8d6642f126b3b8ad94
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Sat Jan 12 00:09:19 2019 +0900
Update notify_all_users.py
commit 85bbfb8365473d430ddd446ad41c0c11f51284f8
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Sat Jan 12 00:01:09 2019 +0900
fix script
commit 870794df093841d391ef3068399164ede50433df
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Fri Jan 11 23:22:57 2019 +0900
update
commit c4c23bf72c6909d34ab38649e584e6fe3208f1df
Author: Shivam <11738908+shivamsingha@users.noreply.github.com>
Date: Thu Feb 14 20:29:32 2019 +0530
Update README.md
Added info about psi being merged into now released stable kernel 4.20
commit 7cdb65c4ba608c8e8cbf40ef17b832d2ec7fbac2
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Feb 12 07:52:46 2019 +0100
Always define MCL_ONFAULT
We detect kernel support at runtime anyway.
https://github.com/rfjakob/earlyoom/issues/113
commit 319e95987f1a031bc95432a6649823dcdf903c96
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Mon Feb 11 22:30:22 2019 +0100
Use mlockall with MCL_ONFAULT to reduce memory usage
Nice saving:
Before: VmRSS: 2196 kB
After: VmRSS: 696 kB
Thanks to @hakavlad for the suggestion at
https://github.com/rfjakob/earlyoom/issues/112 !
commit 3a0b328de1ae2b8619f5a4432161996edb3b955e
Author: Alexey Avramov <hakavlad@gmail.com>
Date: Fri Jan 11 23:48:24 2019 +0900
Update README
commit 101c3bc59d246fe408a3cedff62ff7f245cd143f
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Jan 1 15:46:56 2019 +0100
README: fix CODE_OF_CONDUCT.md link
commit 45dfe8653b45fadf46e358047cbf44f4624debed
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Jan 1 15:46:18 2019 +0100
Update changelog
commit 22bd639f802237fbb425e3bb6b3039438b391bf8
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Wed Dec 5 22:53:17 2018 +0100
notify_all_users.py: catch subprocess exceptions
Dumping the full stack trace is not useful.
commit 0a6e222642c7a4f6a189e15a9af159837f0391c6
Author: rfjakob <jakobunt@gmail.com>
Date: Tue Jan 1 15:41:32 2019 +0100
Create CODE_OF_CONDUCT.md
Requested at https://github.com/rfjakob/earlyoom/issues/102
Closes https://github.com/rfjakob/earlyoom/issues/102
commit a48e82599102c2f079302353b7fa8e2829d32c8e
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Dec 2 14:27:56 2018 +0100
notify_all_users.py: reword message
Fix the "commend" typo, and while we are at it, reword the
message to be more specific.
commit 1464bc14d68136f3a54b124d8877622e4cfacf46
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Dec 2 14:23:57 2018 +0100
Reformat using autopep8
commit c8196f13b8391232396d36ae0295233063c2117f
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Dec 2 14:20:59 2018 +0100
notify_all_users.py: accept arbitrary arguments
commit ca2857e70cab1262013a9acc514edd1112cf1a31
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Dec 2 13:46:27 2018 +0100
Add notify_all_users.py to contrib
Written by hakavlad and posted at
https://github.com/rfjakob/earlyoom/issues/72#issuecomment-439774249
Imported as posted.
commit 0e7c009a787a028984946f245ee3c7dc29eaf3de
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Dec 1 21:16:40 2018 +0100
README: note that deb is available on Debian 10+ and Ubuntu 18.04+
The saves users on older versions from an unpleasant surprise.
https://github.com/rfjakob/earlyoom/issues/99
commit 5b1666fb3f45687e5915c97daec3b905b370e2cb
Author: Boyuan Yang <byang@debian.org>
Date: Sat Nov 3 16:25:08 2018 -0400
Prepare new upload (1.2-1, unstable)
commit c859c5c03de52f156e79383380f6541b93899de3
Merge: a50d894 fe16f8a
Author: yangfl <yangfl@users.noreply.github.com>
Date: Wed Nov 7 13:23:18 2018 +0800
Merge tag 'v1.2'
earlyoom v1.2
commit 0959505414dfea8f6f7335e46b0db48525cd803b
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Nov 4 13:03:39 2018 +0100
Add MANPAGE-render.sh helper script
Allows to quickly view the rendered man page.
commit 8ff3800196686f5016742a8485e604d7eb47670c
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Nov 4 13:03:01 2018 +0100
MANPAGE: document that -S does not work with zero swap
https://github.com/rfjakob/earlyoom/issues/97
commit e600459b563a70d330529ba21625319f80c309de
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Nov 3 16:50:08 2018 +0100
Update README
commit 582ac1bfdaebbe20b94d34519d43aa242c8324de
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Nov 3 16:36:51 2018 +0100
Ignore -S if there is no swap
Instead of exiting with a fatal error, ignore "-S" if there is
zero swap space.
https://github.com/rfjakob/earlyoom/issues/97
commit a8f30d7af3c0475aa6c17413bf1d179ce61470d4
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Nov 3 16:24:58 2018 +0100
Set SIGTERM = SIGKILL if SIGTERM < SIGKILL
As stated in the man page, the preferred way to disable SIGTERM
is to set SIGTERM = SIGKILL.
For a better user experience, don't exit with a fatal error is
the user sets it to zero or below SIGKILL, but fix the value.
https://github.com/rfjakob/earlyoom/issues/97
commit 9485ea399ce9548bc49315f90f2fb16d0b738343
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Nov 1 22:43:19 2018 +0100
Do not clamp SIGTERM < SIGKILL to zero
Not sure if useful, don't do it for now.
commit 28084c321fa223b8d8c4429ef43c5d079f4d4799
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Nov 1 22:23:53 2018 +0100
Allow SIGTERM value below SIGKILL
Saying
earlyoom -m 0,15
disables SIGTERM completely. Allow it.
https://github.com/rfjakob/earlyoom/issues/97
commit b1c04833e0ad2ee455063c159d74ec096c01b094
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Nov 1 21:48:02 2018 +0100
Allow zero SIGKILL value
You can get a zero SIGKILL percentage by using
earlyoom -m 1
so why not allow it on the command line?
https://github.com/rfjakob/earlyoom/issues/97
commit 9a31b838c6e7fc618ccc5d81ba6785844131f3ef
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Nov 1 21:31:07 2018 +0100
Normalize remaining SIGTERM/SIGKILL mentions to uppercase
The first sweep missed a few spots.
commit 79f5d434f0b09ba2abea4bc969f2187d778dd6e6
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Nov 1 21:22:08 2018 +0100
tests: add unit tests for parse_term_kill_tuple
https://github.com/rfjakob/earlyoom/issues/97
commit 7e825feaad01a253385ef39b00c6fd359dc11f82
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Nov 1 20:40:51 2018 +0100
Make parse_term_kill_tuple return an error message
Instead of killing the app, return an error message.
This make this function testable.
commit 23228fb0b5b623e27d2adce7f2c4b87e691a071e
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Nov 1 12:56:06 2018 +0100
MANPAGE: add example for KILL_PERCENT
The new optional KILL_PERCENT is confusing to users,
add examples.
https://github.com/rfjakob/earlyoom/issues/97
commit b52cc566acfb881f97195fc3d5494bf67ff121ea
Author: Mahe <M4he@users.noreply.github.com>
Date: Sun Oct 28 23:09:13 2018 +0100
Add hint about configuration file to README.md
commit 1b84bdecf89448c53910f0405dd02769fe8e9edb
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Mon Oct 29 08:34:06 2018 +0100
Fix test failure
SIGTERM and SIGKILL were changed to uppercase, this needs
to be reflected in the tests.
commit fe16f8ad8dd4f098713771bc12a11359a6fde090
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Oct 28 16:32:08 2018 +0100
Update README for v1.2
commit 92cf1d66f32c76a1a6daa22cd8c11b121100a016
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Oct 28 16:30:09 2018 +0100
MANPAGE: clarify when SIGKILL is sent
commit 52491721298e32b252c26b12afa7d4fa654c4047
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Oct 28 16:29:01 2018 +0100
Show KILL_PERCENT / KILL_SIZE in help text
Show KILL_PERCENT and KILL_SIZE in the help text, and
also normalize SIGTERM and SIGKILL writing style (should be
ALL CAPS).
commit 20e4a016142b1c7b6ab06dba1fc3a905e8d45a26
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Oct 23 23:46:02 2018 +0200
README: add MIT badge
commit 872cd0e6b37c4e4f52cfc2abc10e2bf2f818f165
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Oct 23 23:42:49 2018 +0200
Travis: pull more commits
At the moment Travis build fail because git describe fails.
From the patch:
# Travis by default only pulls the last 50 commits, which means
# "git describe" will fail once we are more than 50 commits
# away from the last tag.
commit ab5810b4d9bf0c7ff8ab7d5d22f58122fa9b2b07
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Oct 23 23:39:22 2018 +0200
README: mention test suite
Mention the test suite and reorder the install instructions
a little.
commit f7933a9bb8ea3e37858b9702270184493cd80d61
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Oct 23 23:32:49 2018 +0200
Makefile: make tests verbose by default
The very terse output of
earlyoom/tests$ go test
PASS
ok _/home/jakob/code/earlyoom/tests 1.447s
makes it look like nothing was actually tested.
commit b41c6a45c2361107212970b7af524ae7754cfecb
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Oct 23 23:28:30 2018 +0200
README: note that -k is now ignored
commit 7314622e03908c5c833439e0ae1742eafeddca9e
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Oct 23 23:22:38 2018 +0200
README: fix link to PSI patches
commit 9a36cd0dd083f08641b7ded244a53a6370bb2523
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Tue Oct 23 23:15:19 2018 +0200
notification: say *why* we kill a process
From https://github.com/rfjakob/earlyoom/issues/92 :
Plus some more explanations should be inserted. Imagine someone gets its hands
one on some pc having this utility installed. At some point he sees the
application he uses disappear with the message Killing process... Some extra
explanations could reduce the overall amount of WTF.
commit a50d8940a05a99e3b87a4d2f17cac5607604011a
Author: Boyuan Yang <byang@debian.org>
Date: Wed Oct 10 15:54:33 2018 -0400
Prepare new upload (1.1-3, unstable)
commit 7f400efc189e83f48fc3a50a3fde80fa5f55e899
Author: Boyuan Yang <byang@debian.org>
Date: Wed Oct 10 15:54:06 2018 -0400
debian/copyright: Update copyright year.
commit 01f5b7b84bebb976011c692cdfa6d7dfd8370e93
Author: Boyuan Yang <byang@debian.org>
Date: Wed Oct 10 15:53:21 2018 -0400
debian/control: Update my uploader email and use the @debian.org one.
commit 44e45a9c9feef123d9e2673453847ae81b447c95
Author: Boyuan Yang <byang@debian.org>
Date: Wed Oct 10 15:52:55 2018 -0400
debian/control: Bump Standards-Version to 4.2.1 (no changes needed).
commit 69b6925d6c196ee80d52cd700966c85169d8295d
Author: Paul "Joey" Clark <joey@neuralyte.org>
Date: Thu Oct 4 10:27:40 2018 +0800
Use the word 'automatically'
commit a81f2e043712242106590c126a181aadef78b64d
Author: Paul "Joey" Clark <joey@neuralyte.org>
Date: Thu Oct 4 10:26:06 2018 +0800
Offer both install and install-initscript in README
commit 4c7f705617b6424c0d228829b629cf69283a2903
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Jul 29 19:40:47 2018 +0200
Fix "Could not set oom_score_adj: Success" message
Error checking was messed up, as fclose overwrites whatever
fprintf may have done.
Fixes https://github.com/rfjakob/earlyoom/issues/90
commit 9822714c3ce404a1cbc475bd621e9a8f03f78911
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Thu Jul 26 20:16:31 2018 +0200
Fix "sending signal took x ms" output if over 1 second
NB: 1 second contains 1000000 microseconds!
commit 048043f851701b97538d44ad9243377b9943b891
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Jul 22 20:14:56 2018 +0200
userspace_kill: add missing newline in error msg
https://github.com/rfjakob/earlyoom/issues/88
commit cea59ca7c5cf7d0d627d49157a4ed9a61f402eb5
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Jul 22 13:35:58 2018 +0200
make format
commit bcd1ad483733522fdc52b6ddb513b766e3c4f43f
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sun Jul 22 13:19:08 2018 +0200
Implement staged kill: first sigterm, then sigkill
Closes https://github.com/rfjakob/earlyoom/issues/67
commit 5f796f90914f9e1b46173f3f6310ec4c17376141
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Jul 21 21:09:43 2018 +0200
tests: don't check for exact "min: 1 %" formatting
Only check that the output contains " 1 %". This keeps
the tests working even if the formatting changes.
commit ffe4e9f107940cb5620e2bba5bd68f92a4af89cc
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Jul 21 15:27:22 2018 +0200
Add colored warnings
![[bug history graph]](https://qa.debian.org/data/bts/graphs/e/earlyoom.png){kind=link}