1ctwatch(1) User Commands ctwatch(1)
2
3
4
6 ctwatch - watch events in a contract or group of contracts
7
9 /usr/bin/ctwatch [-f] [-r] [-v] contract-type... | contract-id...
10
11
13 The ctwatch utility allows a user to observe the events occurring
14 within a set of contracts or contract types. By default, ctwatch
15 watches all contracts.
16
18 The following options are supported:
19
20 -f Report events starting at the front of the event queue. Normally,
21 ctwatch reports only events which occur after it has been
22 invoked. With the -f option, any events that still exist in the
23 contracts' event queues when ctwatch is invoked (for example,
24 unacknowledged critical events) are also reported.
25
26
27 -r Reliably watches all messages. Normally, the system may drop
28 informative events and acknowledged critical events at any time,
29 so ctwatch isn't guaranteed to see them all. This option may only
30 be used if the ctwatch is invoked with the {PRIV_CONTRACT_EVENT}
31 privilege asserted in its effective set.
32
33
34 -v Request verbose event descriptions.
35
36
38 The following operands are supported:
39
40 contract-type Valid contract types are:
41
42 process Process contracts.
43
44
45
46 contract-id A valid contract id.
47
48
50 The following list defines the column headings and the meanings of a
51 ctwatch report:
52
53 CTID The contract ID generating the event.
54
55
56 EVID The event ID.
57
58
59 CRIT Whether the event is informative, critical, or initiates an
60 exit negotiation. Values are info, crit, or neg, respec‐
61 tively.
62
63
64 ACK The event has been acknowledged. Values are yes or "no".
65
66
67 CTTYPE The contract type.
68
69
70 SUMMARY A type-specific summary of the event.
71
72
74 Example 1 Watching a process contract
75
76 example% ctwatch -r 1
77
78 CTID EVID CRIT ACK CTTYPE SUMMARY
79 1 2 crit no process pid 100569 was created
80 1 3 info no process pid 100569 encountered hardware error
81 1 4 info no process pid 100568 exited
82 1 5 info no process pid 100569 exited
83 1 6 crit no process contract empty
84
85
86
88 The following exit values are returned:
89
90 0 Successful completion.
91
92
93 1 An error occurred.
94
95
96 2 Invalid arguments.
97
98
100 /system/contract/*
101
103 See attributes(5) for descriptions of the following attributes:
104
105
106
107
108 ┌─────────────────────────────┬─────────────────────────────┐
109 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
110 ├─────────────────────────────┼─────────────────────────────┤
111 │Availability │SUNWcsu │
112 ├─────────────────────────────┼─────────────────────────────┤
113 │Interface Stability │See below. │
114 └─────────────────────────────┴─────────────────────────────┘
115
116
117 Human Readable Output is Unstable. Invocation is Evolving.
118
120 ctrun(1), ctstat(1), contract(4), process(4), attributes(5), privi‐
121 leges(5)
122
124 Ordering of events is only guaranteed within a single contract, or
125 within a single type when a type is specified.
126
127
128 ctwatch can only observe those events which are generated by contracts
129 owned or authored by processes with the same effective user ID as
130 ctwatch, unless the {PRIV_CONTRACT_OBSERVER} privilege is asserted in
131 its effective set.
132
133
134
135SunOS 5.11 14 Jul 2004 ctwatch(1)