• ConfigVars

All Vesta's Configuration Variables

Under construction. The complete list is spread out on the various man pages.

You can view these config vars with vgetconfig

Author's Choice : Most Frequent

The author comes here more frequently to cut-n-paste this:

vgetconfig Repository VestaSourceSRPC_host

but since we're cutting and pasting, why not have a line for those rare cases when we might be doing sophisticated debug of vesta:

echo `vgetconfig Repository VestaSourceSRPC_host`:`vgetconfig Repository VestaSourceSRPC_port`

UserInterface Section

• The following values are obtained from the [UserInterface] section of the Vesta configuration file (vesta.cfg).

  AppendableRootName

  • The filename under which the global root directory of Vesta repositories is mounted. Ordinarily set to /vesta.

  ForeignParent

  • The the path under which vcheckout -F will create session directories and vbranch -F will create branches. We suggest `vgetconfig UserInterface DefaultPackageParent`/foreign

  MutableRootName

  • The filename under which the local tree of mutable directories provided by Vesta is mounted. Ordinarily set to /vesta-work.

  DefaultPackageParent

  • The default directory to put new packages in. Ordinarily a subdirectory of the appendable root, named with an Internet domain name belonging to the local site. Eg, /vesta1/abc.acme.com/.

  DefaultWorkParent

  • The default parent directory for mutable working directory trees belonging to individual users. Ordinarily the same as the mutable root.

  realm

  • Global user names are formed by appending @realm to the local name.

• TimeFormat

  • A format string for strftime(3) to produce time strings for Vesta attributes. A common setting is "%a %b %e %T %Z %Y".

  FpContent

  • The default value for the vadvance -F flag.

  vadvance_junk

  • The default value for the vadvance -j flag. If not set, the default is "*~ .*~ core".

  vadvance_maxsize

  • The default value for the vadvance -z flag. If not set, the default is 1048576 (1 megabyte).

Evaluator

• DefaultMain

  • Gives one or more default model names to evaluate if none is explicitly specified. Multiple names are given separated by whitesapce, and are tried in order. (For example, if set to "linux_alpha.main.ves linux_ia32.main.ves .main.ves", if a model named "linux_alpha.main.ves" exists it will be evaluated, or if not and a model named "linux_ia32.main.ves" exists it will be evaluated, otherwise if a model named ".main.ves" exists it will be evaluated.) If not set, ".main.ves" is used.

  Switches

  • Specifies evaluator command line switches that will be used on every run. These switches are overridden by any explicit switches used on the evaluator command line.

  MaxThreads

  • Gives the default value for the -maxthreads option; see vesta(1)#-maxthreads

  FpContent

  • Newly created derived files that are strictly less than FpContent bytes long are fingerprinted deterministically according to their contents. Longer files are fingerprinted with arbitrary unique identifiers. The cost of fingerprinting a file's contents is non-trivial, but doing so allows for cache hits in cases where two evaluations depend on files that have identical contents but were created in separate evaluations. The special value -1 causes all files to be fingerprinted by contents, while 0 causes all files to be fingerprinted by unique identifier. (See the documentation for the _run_tool primitive function for more information.)

  server_max_threads

  • A tuning parameter which controls the number of file access callbacks from the repository simultaneously served during a tool invocation. A reasonable value is 4. There's normally no need to change it. (Note that there is no built-in default value.)

  server_max_pending

  • A tuning parameter which controls the number of file access callbacks from the repository held pending while serving other requests. This can be set to a fixed integer, but if the evaluator submits more tool invocations than server_max_threads+server_max_pending, an evaluation failure is likely. If set to "auto", the value used is based on the maximum number of expected requests: either [Repository]threads or the number of evaluator threads (from MaxThreads or the -maxthreads switch if used), whichever is higher, minus server_max_threads. Defaults to "auto".

  NegligibleExternalLoadPerCPU

  • A tuning parameter which controls how hosts are selected for _run_tool() jobs. It is a scaling factor that is multiplied by the number of CPUs in the candidate Run Tool Host. If the load average is below the result of this multiplication and the RunToolServer is running no other jobs, the host is immediately chosen to run the tool invocation. (If not, it may still be chosen later if it's the least loaded candidate host.) If not set, it defaults to 0.75.

CacheServer

• MetaDataRoot

  • See VCache(1).

  Host

  • See ChkptCache(1).

Repository Section

• The following values are obtained from the [Repository] section of the Vesta configuration file.

  VestaSourceSRPC_host

  • The host name of the default (local) repository.

  VestaSourceSRPC_port

  • The default TCP port number for repositories.

  metadata_root

  • umask

    • See repository(8).

Run_Tool

• SRPC_port

  • The default port at which to contact the RunToolServer. (See the next section.)

  get_info_read_timeout

  • Maximum number of seconds that the evaluator will wait for a response from a RunToolServer when getting information about its configuration (OS, architecture, etc.) and number of allowed and currently running tools. This allows the evaluator to give up and move on to another candidate host if one is very slow in responding. Defaults to 120 seconds (2 minutes). (Note that this timeout only applies after a connection is established, and is only provided to guard against misbehaving or overloaded peers.)