2009/9/12 Stathis Kamperis <ekamp...@gmail.com>: > 2. If I leave $1 without double quotes " and the execname doesn't have > a dot in it, it fails with: > $ pfexec ./lala.d temp > dtrace: failed to compile script ./lala.d: line 11: failed to resolve > temp: Unknown variable name Ok, I got lucky with google this time: http://solaris.reys.net/passing-command-line-parameters-to-dtrace-scripts
I have to write: $ pfexec ./lala.d '"temp"' for dtrace to treat it as string argument. > 3. If I surround $1 with double quotes, it fails not matter what the > supplied argument is: > $ pfexec ./lala.d temp.sh > dtrace: failed to compile script ./lala.d: line 31: extraneous > argument 'temp.sh' ($1 is not referenced) > $ pfexec ./lala.d temp > dtrace: failed to compile script ./lala.d: line 31: extraneous > argument 'temp' ($1 is not referenced I still can't figure this out. Does "$1" inside a script make dtrace perceive it as a literal string '$1' ? Cheers, Stathis _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
