Comment 4 for bug 1539719

------- Comment From <email address hidden> 2016-02-03 13:59 EDT-------
dbginfo.sh was modified by canonical. Before it collects data, it aks the user, whether he really wants to do that.

see here:
######################################
# Verification to run as root
#
if test "" -ne 0; then
echo "${SCRIPTNAME}: Error: You must be user root to run \"${SCRIPTNAME}\"!"
exit 1
fi

+ echo "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
+ echo " Warning: The archive created by this utility will contain sensitive"
+ echo " information including, but not limited to:"
+ echo " - configuration files"
+ echo " - log files"
+ echo " - hardware state information"
+ echo " - running process state and command line arguments"
+ echo "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
+ echo ""
+ echo -n " Do you wish to continue? [y/N]> "
+ read resp
+ case "$resp" in
+ y|Y)
+ :
+ ;;
+ *)
+ echo "OK, exiting."
+ exit 0
+ esac
+
+
#######################################
# Parsing the command line
#

IBM can not accept this:
1. It is ensured by the above code, that only the root user is running this script. By default, it is assumed, that the roor user knows what he has to do and what not.
2. For providing debugging information, it is in some cases required to either start dgbinfo.sh immediately at a certain point, or to start it by any automated trigger. The first case will delay the execution of dbginfo.sh, the second will prevent it.
3. For automated testing we often collect data via dbginfo.sh triggered by a script. Same problem, this will not work, or needs some workaround just for this particular flavour of dbginfo.sh

I hereby request to pick up the unmodified code of dbginfo.sh as of s390-tools 1.32.0 provided by IBM.