[0/2] kernel-shark: Be more careful with kshark-su-record

Message

Steven Rostedt July 23, 2019, 10:50 p.m. UTC

Two issues with kshark-su-record.

1) It just calls kshark-record with no path, which can be an issue
   if pkexec removes PATH variable, or sets it to something
   that kshark-record is not in.

2) Need to set DISPLAY variable, because on some of my machines,
   the kshark-record failed to execute due to pkexec removing the
   DISPLAY variable.


Steven Rostedt (VMware) (2):
      kernel-shark: Execute kshark-record from same dir as kshark-su-record
      kernel-shark: Set the DISPLAY environment for pkexec kshark-record

----
 kernel-shark/bin/kshark-su-record | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)