# $1 = path to executable
# $2 = main pid of running program to be traced back.
#
+gdb -quiet -batch -x @scriptdir@/btraceback.gdb $1 $2 2>&1 \
+ | @sbindir@/bsmtp -h @smtp_host@ -s "Bacula traceback" @dump_email@
-gdb -quiet -batch -x @sbindir@/btraceback.gdb $1 $2 2>&1 | mail -s "Bacula traceback" @dump_email@
-
+#
# Below is some old code that did the traceback from a core
-# dump. However, for some odd reason, core dumps are not
-# always produced.
+# dump. However, for security reasons, core dumps of uid=root
+# programs are not always produced.
#i=0
#core=
#echo "In modified btraceback"
#done
#if test x$core != x; then
-# gdb -quiet -batch -x @sbindir@/btraceback.gdb $1 $core 2>&1 | mail -s "Bacula traceback" @dump_email@
+# gdb -quiet -batch -x @scriptdir@/btraceback.gdb $1 $core 2>&1 | mail -s "Bacula traceback" @dump_email@
#else
-# gdb -quiet -batch -x @sbindir@/btraceback.gdb $1 $2 2>&1 | mail -s "Bacula traceback" @dump_email@
+# gdb -quiet -batch -x @scriptdir@/btraceback.gdb $1 $2 2>&1 | mail -s "Bacula traceback" @dump_email@
#fi