Andrew Gallatin writes: > > Since one of the fundamental rules of dtrace is that > > it's safe to use, > > scripts that run forever cannot be allowed. > > I think there's an arguable case for a flag to dtrace to > allow loops. After all, if I'm root, there are plenty > of things I can do to hose a box from the command > line ( cat /dev/random | mdb -kw). Dtrace should > be one of them :)
I think there'd have to be a new privilege constructed (not just "I'm root"), and the entire design of the internal representation would change, and the algorithms would change. It'd be a substantial undertaking ... but, well, it's open source, so ... A much better approach, I think, would be to identify those cases that need special loop-like support, and add extensions to the language that allow you to express things in a safe way. In other words, add something like msgdsize(9F) (but using a known-safe implementation). -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ dtrace-discuss mailing list [email protected]
