Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

btraceback(1) [debian man page]

BTRACEBACK(1)					     Network backup, recovery and verification					     BTRACEBACK(1)

NAME
btraceback - wrapper script around gdb and bsmtp SYNOPSIS
btraceback /path/to/binary pid DESCRIPTION
btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes. USAGE
btraceback is called by the exception handlers of the Bacula daemons during a crash. It can also be called interactively to view the cur- rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below). NOTES
In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must be available in the $PATH. If the Director or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi- leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon. Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the same risks than live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances. Conse- quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem. ENVIRONMENT
btracback relies on $PATH to find the debugger. FILES
/usr/lib/bacula/btraceback The script itself. /usr/sbin/btraceback symbolic link to /usr/lib/bacula/btraceback /etc/bacula/scripts/btraceback.gdb the GDB command batch used to output a stack trace AUTHOR
This manual page was written by Lucas B. Cohen <lbc@members.fsf.org> SEE ALSO
bsmtp(1) Kern Sibbald 6 December 2009 BTRACEBACK(1)

Check Out this Related Man Page

BACULA-DIR(8)					       Network backup, recovery&verification					     BACULA-DIR(8)

NAME
bacula-dir - Bacula Director SYNOPSIS
bacula-dir [options] DESCRIPTION
This manual page documents briefly the bacula-dir command. Bacula's Director Daemon acts as the controller of the network backup system: it is responsible for scheduling and coordinating backups across the network. OPTIONS
-c file Specify the configuration file to use. -d nn Set debug level to nn. -dt Print timestamp in debug output. -f Run in foreground (for debugging). -g group Set the group/gid to run as. -m Print kaboom output (for debugging) -r job Run <job>. -s No signals (for debugging). -t Test the configuration file and report errors. -u user Set the username/uid to run as. -v Set verbose mode. -? Show version and usage of program. TCP-WRAPPERS CONFIGURATION Tcpwrappers looks for the service name of the bacula daemons in hosts.allow , and the service names of these daemons is configured to be different from the binary. The service names are configured to be %hostname%-%component% rather than bacula-dir (As defined in the bacula- dir.conf.in file) So the hosts.allow entry has to match %hostname%-%component% (servername-dir for example) instead of bacula-%component% WARNING: This means that if the hosts.allow file has the entry: bacula-dir: ALL you will not be able to run bconsole to connect to the local director! The entry would have to read: server-dir: ALL and this will allow the console to connect to the director. (The process running is bacula-dir.) SEE ALSO
bacula-fd(8), bacula-sd(8). AUTHOR
This manual page was written by Jose Luis Tallon <jltallon@adv-solutions.net>. Kern Sibbald 6 December 2009 BACULA-DIR(8)
Man Page