@@ -173,19 +173,19 @@ Specific to arangod, move to programs detail page?
173
173
Does the resolution order for config files apply to all binaries?
174
174
Linux only? Also macOS? Windows not addressed so far.
175
175
176
- If this command is not passed to the server, then by default, the server will
177
- attempt to first locate a file named * ~ /.arango/arangod.conf* in the user's home
176
+ If this command is not passed to the server, then by default, the server
177
+ attempts to first locate a file named ` ~/.arango/arangod.conf ` in the user's home
178
178
directory.
179
179
180
- If no such file is found, the server will proceed to look for a file
181
- * arangod.conf* in the system configuration directory. The system configuration
180
+ If no such file is found, the server proceeds to look for a file
181
+ ` arangod.conf ` in the system configuration directory. The system configuration
182
182
directory is platform-specific, and may be changed when compiling ArangoDB
183
- yourself. It may default to * /etc/arangodb* or * /usr/local/etc/arangodb* . This
183
+ yourself. It may default to ` /etc/arangodb ` or ` /usr/local/etc/arangodb ` . This
184
184
file is installed when using a package manager like rpm or dpkg. If you modify
185
185
this file and later upgrade to a new version of ArangoDB, then the package
186
186
manager normally warns you about the conflict. In order to avoid these warning
187
187
for small adjustments, you can put local overrides into a file
188
- * arangod.conf.local* .
188
+ ` arangod.conf.local ` .
189
189
{% endcomment %}
190
190
191
191
## Suffixes for Numeric Options
@@ -200,6 +200,7 @@ in megabytes, gigabytes, or terabytes.
200
200
| ` mib ` , ` MiB ` , ` MIB ` | 1024<sup >2</sup > | 1,048,576 | ` 64mib ` |
201
201
| ` gib ` , ` GiB ` , ` GIB ` | 1024<sup >3</sup > | 1,073,741,824 | ` 3GIB ` |
202
202
| ` tib ` , ` TiB ` , ` TIB ` | 1024<sup >4</sup > | 1,099,511,627,776 | ` 3tib ` |
203
+ | ` b ` , ` B ` | 1 | 1 | ` 10b ` |
203
204
| ` k ` , ` K ` , ` kb ` , ` KB ` | 1000 | 1,000 | ` 3k ` |
204
205
| ` m ` , ` M ` , ` mb ` , ` MB ` | 1000<sup >2</sup > | 1,000,000 | ` 3M ` |
205
206
| ` g ` , ` G ` , ` gb ` , ` GB ` | 1000&l
6D40
t;sup >3</sup > | 1,000,000,000 | ` 3GB ` |
@@ -286,29 +287,29 @@ level = startup=info
286
287
There are built-in defaults, with which all configuration variables are first
287
288
initialized. They can be overridden by configuration files and command line
288
289
options (in this order). Only a fraction of all available options are set in
289
- the configuration files that ArangoDB ships with. Many options will therefore
290
+ the configuration files that ArangoDB ships with. Many options therefore
290
291
fall back to the built-in defaults unless they are overridden by the user.
291
292
292
293
It is common to use modified configuration files together with startup
293
294
options on a command line to override specific settings. Command line options
294
295
take precedence over values set in a configuration file.
295
296
296
297
If the same option is set multiple times, but only supports a single value,
297
- then the last occurrence of the option will become the final value.
298
- For example, if you edit ` arangosh.conf ` to set :
298
+ then the last occurrence of the option becomes the final value.
299
+ For example, if you edit ` arangosh.conf ` as follows :
299
300
300
- ```
301
+ ``` conf
301
302
server.database = myDB1
302
303
server.database = myDB2
303
304
```
304
305
305
- … and start ArangoShell like:
306
+ Then start ArangoShell like this :
306
307
307
308
```
308
309
arangosh --server.database myDB3 --server.database myDB4
309
310
```
310
311
311
- … then the database it will connect to is ` myDB4 ` , because this startup option
312
+ The database it connects to is ` myDB4 ` , because this startup option
312
313
takes a single value only (i.e. it is not a vector), the built-in default
313
314
is ` _system ` but the configuration file overrules the setting. It gets set to
314
315
` myDB1 ` temporarily before it is replaced by ` myDB2 ` , which in turn gets
0 commit comments