NNAAMMEE
       db_deadlock - the DB database deadlock detector

SSYYNNOOPPSSIISS
       ddbb__ddeeaaddlloocckk [--vvww] [--aa mm || oo || yy] [--hh hhoommee] [--LL ffiillee ] [--tt sseecc ]

DDEESSCCRRIIPPTTIIOONN
       The _d_b___d_e_a_d_l_o_c_k utility traverses the database lock struc-
       tures and aborts a transaction  each  time  it  detects  a
       deadlock.  This utility should be run as a background dae-
       mon whenever multiple threads or processes are using lock-
       ing.   By  default,  a  random transaction involved in the
       deadlock is aborted.

       The options are as follows:

       --aa   When a deadlock is detected, abort the oldest (``o'')
            transaction, the youngest (``y'') transaction, or the
            transaction with the minimum number of locks (``m'').

       --hh   Specify a home directory for the database.

       --LL   Log  the  execution of the db_deadlock utility to the
            specified file in the following format, where ``###''
            is the process ID, and the date is the time the util-
            ity starting running.

            db_deadlock: ### Wed Jun 15 01:23:45 EDT 1995

            This file will be removed if the db_deadlock  utility
            exits gracefully.

       --tt   Initiate  a  pass  over  the  database locks at least
            every _s_e_c seconds.

       --vv   Run in verbose mode, generating  messages  each  time
            the detector runs.

       --ww   Make a single pass over the database locks every time
            a process is forced to wait for a lock.

       At least one of the --tt and --ww options must be specified.

       The _d_b___d_e_a_d_l_o_c_k  utility  attaches  to  DB  shared  memory
       regions.   In  order to avoid region corruption, it should
       always be given the chance to detach and exit  gracefully.
       To  cause  _d_b___d_e_a_d_l_o_c_k  to clean up after itself and exit,
       send it an interrupt signal (SIGINT).

       The _d_b___d_e_a_d_l_o_c_k utility exits 0 on success, and >0  if  an
       error occurs.

EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS
       The  following  environment variables affect the execution
       of _d_b___d_e_a_d_l_o_c_k:

       DB_HOME
            If the --hh option is not specified and the environment
            variable  _D_B___H_O_M_E  is  set, it is used as the path of
            the database home, as described in _d_b___a_p_p_i_n_i_t(3).

SSEEEE AALLSSOO
       The DB library is a family of  groups  of  functions  that
       provides  a  modular programming interface to transactions
       and record-oriented file  access.   The  library  includes
       support  for  transactions, locking, logging and file page
       caching, as well as various indexed access methods.   Many
       of  the  functional  groups  (e.g.,  the file page caching
       functions) are useful independent of the  other  DB  func-
       tions,  although  some  functional  groups  are explicitly
       based on other functional groups (e.g.,  transactions  and
       logging).   For  a  general description of the DB package,
       see _d_b___i_n_t_r_o(3).

       _d_b___a_r_c_h_i_v_e(1), _d_b___c_h_e_c_k_p_o_i_n_t(1), _d_b___d_e_a_d_l_o_c_k(1), _d_b___d_u_m_p(1),
       _d_b___l_o_a_d(1), _d_b___r_e_c_o_v_e_r(1), _d_b___s_t_a_t(1), _d_b___i_n_t_r_o(3),
       _d_b___a_p_p_i_n_i_t(3), _d_b___c_u_r_s_o_r(3), _d_b___d_b_m(3), _d_b___i_n_t_e_r_n_a_l(3),
       _d_b___l_o_c_k(3), _d_b___l_o_g(3), _d_b___m_p_o_o_l(3), _d_b___o_p_e_n(3), _d_b___t_h_r_e_a_d(3),
       _d_b___t_x_n(3)