Sar sends SIGTERM to init

Bug #1511778 reported by BrandonTomlinson on 2015-10-30
8
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://github.com/sysstat/sysstat/commit/c3de69658006af0e0e3b7746e8646b8b4cdd2860 .

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);

BrandonTomlinson (druke) wrote :

Updated steps to reproduce:

sar -b 1 100 > /dev/null &
kill -SIGKILL $! ; kill -SIGINT $(pidof sadc);

description: updated
Robert Luberda (robert-debian) wrote :

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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers