+++ This bug was initially created as a clone of Bug #348981 +++

Description of problem:

Sysreport in HREL 5.0 issues sysrq-t by default
Version-Release number of selected component (if applicable):


How reproducible:

Always
Steps to Reproduce:
1. Run sysreport command with no options
2.
3.
  
Actual results:

Sysreport runs and echos "t" to /proc/sysrq-trigger and other sysrq commands

Expected results:

Sysrq-t should not be issued by default
Additional info:

This went in as a feature but it's really a regression. Issuing sysrq should
only be done in specific circumstances. It should not be done as a routine
practice when sysreport is normally run. Sysrq-t can cause a large variety of
problems including applicaiton failover, scsi resets/timeouts, bonding failover,
and application hangs.

-- Additional comment from than@redhat.com on 2007-10-24 04:55 EST --
it seems a critical bug. We should probably release the fix.

-- Additional comment from pknirsch@redhat.com on 2007-10-24 06:37 EST --
Suggesting for RHEL-3.9 and giving Devel ACK as the fix is simple and important.

Read ya, Phil

-- Additional comment from rbiba@redhat.com on 2007-10-25 11:37 EST --
QA ACK for RHEL 3.