cellular-infrastructure
/
osmo-gsm-tester
mirror of https://gerrit.osmocom.org/osmo-gsm-tester
9
0
Fork 0
Code Issues Releases Wiki Activity

doc/manual: Fix links to nonexistent sections 

Change-Id: I8742fa9c41d3ab95d41e299179df19c3d1e0a65b
This commit is contained in:
Pau Espin 2020-06-10 17:49:55 +02:00
parent 0a5011047a
commit ffa325ede0
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/manuals/chapters/config.adoc
View File

@ -326,15 +326,15 @@ should be used.
A 'resources.conf' is validated by the <<schema_resources,resources schema>>.
That means it is structured as a list of items for each resource type, where
each item has one or more attributes -- for an example, see
<<resources_conf_example>>.
each item has one or more attributes -- looking for an example, see {app-name}
subdirectory _doc/examples_.
Side note: at first sight it might make sense to the reader to rather structure
e.g. the 'ip_address' or 'arfcn' configuration as +
'"arfcn: GSM-1800: [512, 514, ...]"', +
but the more verbose format is chosen to stay consistent with the general
structure of resource configurations, which the resource allocation algorithm
uses to resolve required resources according to their traits. These
but the more verbose format is chosen in general to stay consistent with the
general structure of resource configurations, which the resource allocation
algorithm uses to resolve required resources according to their traits. These
configurations look cumbersome because they exhibit only one trait / a trait
that is repeated numerous times. No special notation for these cases is
available (yet).

4
doc/manuals/chapters/install.adoc
View File

@ -309,7 +309,7 @@ Details:
wide install, in which case you could omit the explicit PATH to
"$PWD/osmo-gsm-tester/src".
*** This assumes that there are configuration files for osmo-gsm-tester placed
on the system (see <<config_paths>>).
on the system (see <<config_main>>).
*** If you'd like to check the behavior of test failures, you can uncomment the
line below "# debug" to produce a build failure on every run. Note that
this test typically produces a quite empty run result, since it launches no
@ -687,4 +687,4 @@ sed -i 's#\./suites#/usr/local/src/osmo-gsm-tester/suites#' osmo-gsm-tester/path
----
NOTE: The configuration will be looked up in various places, see
<<config_paths>>.
<<config_main>>.