Sar sends SIGTERM to init
Bug #1511778 reported by
BrandonTomlinson
on 2015-10-30
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | sysstat (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
This only affects Trusty and vivid releases, it was fixed upstream in https:/
At this point, trusty's sar can still pass SIGTERM (and other sigs) up to init.
We're able to reproduce with something like:
sar -b 1 100 > /dev/null &
kill -SIGKILL $! ; kill -SIGINT $(pidof sadc);
| Robert Luberda (robert-debian) wrote : | #2 |
This was fixed in sysstat 11.1.3-1
| Changed in sysstat (Ubuntu): | |
| status: | New → Incomplete |
| status: | Incomplete → Fix Released |
To post a comment you must log in.
Updated steps to reproduce:
sar -b 1 100 > /dev/null &
kill -SIGKILL $! ; kill -SIGINT $(pidof sadc);