Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
Chutney
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
George Kadianakis
Chutney
Commits
b86168c2
Unverified
Commit
b86168c2
authored
8 years ago
by
teor (Tim Wilson-Brown)
Browse files
Options
Downloads
Patches
Plain Diff
Document all the test-network.sh arguments in the README
Well, accept for --dry-run, which is an implementation detail.
parent
4f8dc020
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+14
-1
14 additions, 1 deletion
README
with
14 additions
and
1 deletion
README
+
14
−
1
View file @
b86168c2
...
...
@@ -23,8 +23,21 @@ Automated Setup, Verification, and Shutdown:
./tools/test-network.sh --tor-path <tor-build-directory>
./tools/test-network.sh --tor <name-or-path> --tor-gencert <name-or-path>
(--tor-path and $TOR_DIR override --tor and --tor-gencert.)
./tools/test-network.sh --chutney-path <chutney-directory>
(The script is pretty good at guessing this.)
The environmental variables documented below also work with test-network.sh.
test-network.sh looks for some tor binaries (either in a nearby build
directory or in your $PATH), configures a comprehensive tor test network,
launches it, then verifies data transmission through it, and cleans up after
itself.
You can modify its configuration using command-line arguments, or use the
chutney environmental variables documented below:
--delay CHUTNEY_BOOTSTRAP_TIME
--data CHUTNEY_DATA_BYTES
--connections CHUTNEY_CONNECTIONS
--hs-multi-client CHUTNEY_HS_MULTI_CLIENT
Standard Actions:
./chutney configure networks/basic
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment