[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
|
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
442.0. "DEADlock search reporting" by IOSG::BAILEY (Plug in \Turn on \Tune out) Fri Apr 10 1987 06:43
VPA is reporting a large number of Deadlock search's on one of
our clusters, these search's may/may not be caused by user
applications rather than 'system' programs, is there any way we
could find out
. WHO has the resource that is causing the search ?
. WHAT is the resource ?
The only answer I can think of is to put an SPM trace point in
the deadlock code (at LCK$BREAK_DEADLOCK ?) to return some data,
but is there a better way ?
With Thanks
Peter (PEB) Bailey
(Also posted in VMSNOTES & CLUSTER notes)
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 442.1 | SPM works fine.. | IOSG::BAILEY | Plug in \Turn on \Tune out | Mon Apr 13 1987 13:43 | 0
|