"tusc" interfering with a running program

[Rodney Hills]

Can "tusc" change the behaviour of a program it is monitoring?

When I was monitoring a daemon that did a fork, the fork would fail.

Any feedback on how "safe" tusc is?

Thanks

-- Rod Hills

[Steven E. Protter]

I have never seen tusc bother a running process.

I have used tusc to trace a process that was an Ignite image push, generating 2.5 GB of diagnostic data.

The way its used, you hang it on a process, which is no different in function than doing something like performance monitoring.

SEP

[Rodney Hills]

Could it cause a "timing" issue?

Maybe the 2 programs are talking through a pipe and with tusc tracing one process takes a little longer to run, and a time-out occurs...

-- Rod Hills

[Steven E. Protter · Accepted solution]

I've run the top command while tusc was running. It showed up on the list as active, but was not using a lot of resources.

With any additional process, it does effect overall performance, but not in a noticeable way.

I think if you thought about a way for tusc to cause trouble and implemented that scenario, you could cause it.

With normal use however, I can't see timeout issues happening. Ignite is prety resource intensive, and I saw no adverse results. better yet, it showed me an error message that was not returned to the Ignite log and allowed me to solve a four week old problem instantly.

SEP

[Rodney Hills]

I plan on using "tusc" more since it does provide so much good information.

Maybe the problem I was seeing was some other problem and not tusc induced.

Thanks again...

-- Rod Hills