> As a workaround, you might try running with the -w flag ("permit
> destructive actions".) This will skip the deadman timeout processing.
> (This will only work if you're running as root, though.)
I may end up doing that. I'm concerned that it is stopping for a reason
however, and would like to see if I can get it working without needing to
turn on destructive actions.> I'm curious, though, what hardware is this? I've seen similar > behavior before on an x4600 (16 cores) that was likely a problem with > skewed tsc values that cause some gethrtime() weirdness. This is two dual-core Opterons. -- Mark Harrison Systems Administrator OmniTI Computer Consulting, Inc.
signature.asc
Description: Digital signature
_______________________________________________ dtrace-discuss mailing list [email protected]
