Running tccd from the command line
This information is not applicable to Win32 systems.
Most modern UNIX systems support
so most people will build the
(the Test Case Controller daemon).
However, there are some situations where it is required to run
from the command line.
If you need to do this for some reason it is best to build the
Some hints about how best to do this are presented in this article.
When you run
from the command-line, it inherits all your
This can result in test cases being influenced by your environment in a
way that can't be repeated on someone else's system.
This can cause a lot of trouble if you develop a test suite that works
OK for you, but fails in various ways when you ship it to a customer.
In order to ensure that you don't fall in to this trap when developing a
test suite, it is necessary to start
with a known clean environment.
You can use the
command to do this, and put the correct invocation
in a shell script.
exec env - PATH=$PATH TZ=$TZ . . . tccd [ options . . .]
argument to the
command cleans out the environment for the command
to be executed.
Then you should specify just the list of environment variables that you
actually need to run test cases.
This issue is less of a problem when starting
on the local system (system 0) because
sends all of its environment to
on system 0 when it logs on.
But it is important to run
in a known environment on remote
systems, because in this case the environment is not sent.
In the past a number of people have been caught out by not taking care
of this issue when starting
from the command-line.
If you run
as yourself, it will be unable to change its
user ID to
This results in an error message in the
will still run (using your user ID) provided your
user ID and group ID are each >= 100.
You can use the command:
tccd -u your-login-name
if you want to avoid the error message being printed.
in the TETware Installation Guide for UNIX Operating Systems.
manual page in the TETware User Guide.