I don't have a lot of disk space so I seldom leave it on. Otherwise - there
seems to be little effect. netmon.trace and trapd.trace files grow quickly!
-----Original Message-----
From: Todd H. [mailto:netview@toddh.net]
Sent: Wednesday, March 06, 2002 9:55 PM
To: Ray Westphal
Cc: Scott Bursik; nv-l@lists.tivoli.com
Subject: impact of tracing (was: Re: [nv-l] No events displayed)
"Ray Westphal" <westphal@accessus.net> writes:
> Hello Scott,
>
> If you have tracing enabled on trapd daemon, run the trapd -T
> command to start a trace. (See the serversetup trapd configuration.)
> Wait about 30 seconds and run the command again to stop the
> trace. Usually the trace will dump to /usr/OV/log/trapd.trace. Edit
Speaking of tracing--how much overhead does it put on the NetView
processes does daemon tracing add? Is it simply out the question
to run with it on? If so, how much additional delay would one expect?
Granted, disk space is a concern, but in terms of overall server
performance? I'm just trying to get a sense of whether the option
is so invasive that it'll slow everything down dramatically.
--
Todd H.
http://www.toddh.net/
|