GNU Rush |
|
Restricted User Shell |
Sergey Poznyakoff |
GNU Rush provides a special test mode, intended to test
configuration files and to emulate execution of commands. Test
mode is enabled by the --test command line option (aliases:
--lint, -t). When rush
is given this option, the
following occurs:
rush
processes
its argument as usual (see Operation), except that the command
itself is not executed.
rush
emulates interactive usage, but does not execute the final command.
An exit status of 0 means no errors, 1 means an error has occurred.
You can also emulate access by a particular user, by supplying his user name via the --user (-u) option. This option implies --test.
In test mode, you can set debugging level (see Debugging) from the command line, using the --debug (-d) command line option. It expects a single number specifying debugging level as its argument. The debugging level set this way overrides settings from the configuration file.
Here are several examples that illustrate the use of test mode in various cases:
$ rush --test
$ rush --test sample.rc
$ rush --test -i sample.rc
cvs server
. Use debugging level 2:
$ rush --test --debug=2 -c "cvs server"
$ rush --user=jeff --debug=2 -c "cvs server"
Note, that you don’t need to specify --test along with --user or -i options.
$ rush --test --debug=2 -c "cvs server" sample.rc
This document was generated on January 2, 2022 using makeinfo.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.