Penguin
Recent Changes
Blame: db_deadlock(1)
EditPageHistoryDiffInfoLikePages
Annotated edit history of db_deadlock(1) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 DB_DEADLOCK
2 !!!DB_DEADLOCK
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 ENVIRONMENT VARIABLES
7 SEE ALSO
8 ----
9 !!NAME
10
11
12 db_deadlock - the DB database deadlock detector
13 !!SYNOPSIS
14
15
16 __db_deadlock__ [[__-vw__] [[__-a m | o | y__] [[__-h home__]
17 [[__-L file__ ] [[__-t sec__ ]
18 !!DESCRIPTION
19
20
21 The ''db_deadlock'' utility traverses the database lock
22 structures and aborts a transaction each time it detects a
23 deadlock. This utility should be run as a background daemon
24 whenever multiple threads or processes are using locking. By
25 default, a random transaction involved in the deadlock is
26 aborted.
27
28
29 The options are as follows:
30
31
32 __-a__
33
34
35 When a deadlock is detected, abort the oldest (``o'')
36 transaction, the youngest (``y'') transaction, or the
37 transaction with the minimum number of locks
38 (``m'').
39
40
41 __-h__
42
43
44 Specify a home directory for the database.
45
46
47 __-L__
48
49
50 Log the execution of the db_deadlock utility to the
51 specified file in the following format, where ``###'' is the
52 process ID, and the date is the time the utility starting
53 running.
54
55
56 db_deadlock: ### Wed Jun 15 01:23:45 EDT 1995
57
58
59 This file will be removed if the db_deadlock utility exits
60 gracefully.
61
62
63 __-t__
64
65
66 Initiate a pass over the database locks at least every
67 ''sec'' seconds.
68
69
70 __-v__
71
72
73 Run in verbose mode, generating messages each time the
74 detector runs.
75
76
77 __-w__
78
79
80 Make a single pass over the database locks every time a
81 process is forced to wait for a lock.
82
83
84 At least one of the __-t__ and __-w__ options must be
85 specified.
86
87
88 The ''db_deadlock'' utility attaches to DB shared memory
89 regions. In order to avoid region corruption, it should
90 always be given the chance to detach and exit gracefully. To
91 cause ''db_deadlock'' to clean up after itself and exit,
92 send it an interrupt signal (SIGINT).
93
94
95 The ''db_deadlock'' utility exits 0 on success, and
96 ''
97 !!ENVIRONMENT VARIABLES
98
99
100 The following environment variables affect the execution of
101 ''db_deadlock'':
102
103
104 DB_HOME
105
106
107 If the __-h__ option is not specified and the environment
108 variable ''DB_HOME'' is set, it is used as the path of
109 the database home, as described in
110 ''db_appinit''(3).
111 !!SEE ALSO
112
113
114 The DB library is a family of groups of functions that
115 provides a modular programming interface to transactions and
116 record-oriented file access. The library includes support
117 for transactions, locking, logging and file page caching, as
118 well as various indexed access methods. Many of the
119 functional groups (e.g., the file page caching functions)
120 are useful independent of the other DB functions, although
121 some functional groups are explicitly based on other
122 functional groups (e.g., transactions and
123 logging).
124
125
126 ''db_archive''(1), ''db_checkpoint''(1),
127 ''db_deadlock''(1), ''db_dump''(1), ''db_load''(1),
128 ''db_recover''(1), ''db_stat''(1),
129 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.