scrunner.conf − scrunner configuration file The files and contain information used to configure the scrunner command. The format is identical for both files. These configuration files specify a java command, java system properties, and classpath entries in a directive, section, a section, and a section. A section is terminated by any of the above directives or by a line containing with no preceding or following characters other than whitespace. Each section and directive is optional. After leading and trailing whitespace is deleted, lines that start with and all empty lines are ignored. Each section of the configuration file has its own syntax. The %java directive consists of the string followed by whitespace and then a file name.
This entry is optional. If not present a default value for is used to give the location of the java command. Normally this directive is not needed. Exceptions include testing a version of java not yet installed.

This section contains java property definitions and directives indicating that definitions apply only for a specific scripting language. Excluding comments and blank lines, each line consists of one of the following two alternatives.
The identifier is given a value specified by As a convenience, if starts with then is replaced with a single Otherwise if VALUE starts with then is replaced with the user´s home directory. All other characters are kept as is. There is an exception when has the value in this case, the value is a path and the substitution for described above applies to each component of the path.
This denotes the start of a scripting-language-specific subsection, which continues until the next directive, another top-level directive, or until a terminating directive is seen. For the directive, is the "official" name of the scripting language as defined in the Java specifications. Each line (excluding comments and blank lines) contains a component of a module path, either a directory or a jar file. If the line starts with then is replaced with a single Otherwise if VALUE starts with then is replaced with the user´s home directory. In addition, if VALUE starts with followed by the file separator ("/" on Unix or Linux) then is replaced with the directory in which the Bzdev class library´s JAR file is located. Modulepath components can be scripting-language dependent. As in the section, a line of the form
indicates the start of a set of module path components (one per line) that are to be included in the module path when the official name of the scripting language is Each language-specific sequence is terminated by either a top-level directive, an line, or another line. Libraries needed to install to determine if a scripting language is supported, its aliases, etc., should not be in a language-specific part of the classpath-components section. Each line (excluding comments and blank lines) contains a pathname entry, either a directory or a jar file. If the line starts with then is replaced with a single Otherwise if VALUE starts with then is replaced with the user´s home directory. In addition, if VALUE starts with followed by the file separator ("/" on Unix or Linux) then is replaced with the directory in which the Bzdev class library´s JAR file is located. If the last component in a path name is preceded by a file separator ("/" on Unix or Linux), then the entry denotes all jar files in that directory preceding the last file separator character on the line. Classpath components can be scripting-language dependent. As in the section, a line of the form     
indicates the start of a set of class path components (one per line) that are to be included in the class path when the official name of the scripting language is Each language-specific sequence is terminated by either a top-level directive, an line, or another line. Libraries needed to install to determine if a scripting language is supported, its aliases, etc., should not be in a language-specific part of the classpath-components section. Configuration files are searched in a particular order: followed by (both files are optional in that missing ones are skipped). The following directives can be used to configure to support Python, using the Jython implementation (the configuration shown is for a Debian Linux system and assumes a particular version of Jython):
%defs
%lang python
python.cachedir = ~/.jython-cachedir
%end
%classpath.components
/usr/share/java/jython-engine.jar
/usr/share/java/jython.jar
%end
System configuration file, read by all users. On some systems (e.g., Solaris), the path is User configuration file, where "~" represents the user´s home directory, read by the current user only.