[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-dtrace-discuss
Subject:    Re: [dtrace-discuss] Re: Re: Using DTrace to monitor productions #ms
From:       Nicolas Williams <Nicolas.Williams () Sun ! COM>
Date:       2006-12-20 17:39:14
Message-ID: 20061220173913.GI26175 () binky ! Central ! Sun ! COM
[Download RAW message or body]

On Wed, Dec 20, 2006 at 06:25:20PM +0100, Andreas.Haas@Sun.COM wrote:
> On Wed, 20 Dec 2006, Nicolas Williams wrote:
> >See ctrun(1), ctwatch(1) and contract(4).

In fact, if you're scripting job launch/monitoring then using ctrun(1)
and ctwatch(1) may be best -- no C code to write.

Yes, ctwatch(1)'s output is not Committed, but you can probably deal.
BTW, IMO, that's a bug; file a CR if you need stable output from
ctwatch(1).

The best part is you get to let the customer specify fatal events and
restart semantics in a way that is consistent with ctrun and SMF.

Nico
-- 
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
[prev in list] [next in list] [prev in thread] [next in thread]