> What should the behavior of 'dtrace -c' be when dtrace(1M) exits > before the target command? Should the target process be killed, or > should the target process continue running? > > Currently, the target process keeps running, but this also happens in > the case when dtrace(1M) exits with an error (see > http://bugs.opensolaris.org/view_bug.do?bug_id=6712247.) ...
IMHO, I think it should work just like it does now. I don't want the D program that is monitoring my process to have that kind of control, unless I specifically tell it to do so. What if I'm only interested in monitoring the first part of the execution? Also, even if my D program exits with an error, I'm still not sure I want it killing my process. What if my application had already started doing something that was part of a bigger transaction that needed to complete in order to not leave a file in a precarious state. I realize the odds are against that, but the idea just bothers me on principle. ;-) It seems like it would be a better fix to not start the "-c" program until the D script compiles cleanly. Is that possible? Chip _______________________________________________ dtrace-discuss mailing list [email protected]
