jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1332684 - /jmeter/trunk/xdocs/usermanual/component_reference.xml
Date Tue, 01 May 2012 15:03:35 GMT
Author: sebb
Date: Tue May  1 15:03:34 2012
New Revision: 1332684

Some details on running commands


Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Tue May  1 15:03:34 2012
@@ -1708,6 +1708,28 @@ The OS Process Sampler is a sampler that
 It should allow execution of any command that can be run from the command line.<br></br>
 Validation of the return code can be enabled, and the expected return code can be specified.<br></br>
+Note that OS shells generally provide command-line parsing. 
+This varies between OSes, but generally the shell will split parameters on white-space.
+Some shells expand wild-card file names; some don't.
+The quoting mechanism also varies between OSes.
+The sampler deliberately does not do any parsing or quote handling.
+The command and its parameters must be provided in the form expected by the executable.
+This means that the sampler settings will not be portable between OSes.
+Many OSes have some built-in commands which are not provided as separate executables. 
+For example the Windows DIR command is part of the command interpreter (CMD.EXE).
+These built-ins cannot be run as independent programs, but have to be provided as arguments
to the appropriate command interpreter.
+For example, the Windows command-line: <b><code>DIR C:\TEMP</code></b>
needs to be specified as follows:
+command:   CMD
+Param 1:   /C
+Param 2:   DIR
+Param 3:   C:\TEMP
 <property name="Check Return Code" required="No">If checked, sampler will compare return
code with Expected Return Code.</property>

View raw message