Displaying 2 results from an estimated 2 matches for "usr_exec".
Did you mean:
sm_exec
2008 Apr 28
3
[Bug 1657] New: tests/functional/acl/nontrivial/ zfs_acl_cp_001_pos causes panic
...N: Compress will keep file attribute intact after the
file is compressed and uncompressed
stdout| 03:02:07 SUCCESS: set_cur_usr root
stdout| 03:02:08 SUCCESS: create_files /testdir106790
stdout| 03:02:09 SUCCESS: cksum_files /testdir106790/INIT BEFORE_FCKSUM
BEFORE_ACKSUM
stdout| 03:02:09 SUCCESS: usr_exec /usr/bin/compress
/testdir106790/INIT/file.116844.0 /testdir106790/INIT/file.116844.1
/testdir106790/INIT/file.116844.2 /testdir106790/INIT/file.116844.3
/testdir106790/INIT/file.116844.4
stdout| 03:02:09 SUCCESS: usr_exec /usr/bin/mv
/testdir106790/INIT/file.116844.0.Z /testdir106790/INIT/file.116...
2008 Aug 19
3
variables in dtrace scripts
Greetings,
is there a way to specify probes and other dtrace operations via command
line parameters, like
"
BEGIN
{
usr_exec=$$1;
usr_syscall=$$2;
}
syscall::usr_syscall:entry
/execname == usr_exec && guard++ == 0/
{
...
"
[this does not work]
This would make it possible to create "generic" dtrace scripts.
Otherwise, some shellscript with sed-magic would need to be used.
thanks Joachim...