1
0
Fork 0
mirror of https://github.com/transmission/transmission synced 2025-01-03 05:25:52 +00:00

Fix broken links

Charles Kerr 2020-04-30 16:46:08 -05:00
parent 945e24af1e
commit a12ce5994c

@ -20,7 +20,6 @@
</table>
Some Linux distributions' start script for transmission-daemon use different location. This varies by distribution, but two paths sometimes used are `/var/lib/transmission-daemon` and `/var/run/transmission`.
Locations for [[Debian|UnixServer/Debian]] and its derivatives (e.g. Ubuntu).
If you want to swap between the two applications, all you have to do is pass in a different config directory with the -g command-line option. For example, to have the daemon pick up where the gtk+ client left off, run `transmission-daemon -g ~/.config/transmission`.
@ -35,7 +34,7 @@ If you want to swap between the two applications, all you have to do is pass in
### Overriding the Defaults
The per-user configuration folder's location can be overridden by setting `TRANSMISSION_HOME` and/or other [[environment variables|EnvironmentVariables]].
The per-user configuration folder's location can be overridden by setting `TRANSMISSION_HOME` and/or other [[environment variables|Environment-Variables]].
## Files
@ -43,7 +42,7 @@ The configuration folder typically has the following files:
### settings.json
This is a json-encoded file that holds all the client's settings and preferences. It's currently only used by the daemon, GTK+ and CLI clients. json was chosen because it's mostly human-readable and -writable, but also allows data hierarchies to be stored. See the [[Editing Configuration Files|EditConfigFiles]] page on how to modify them.
This is a json-encoded file that holds all the client's settings and preferences. It's currently only used by the daemon, GTK+ and CLI clients. json was chosen because it's mostly human-readable and -writable, but also allows data hierarchies to be stored. See the [[Editing Configuration Files|Editing-Configuration-Files]] page on how to modify them.
### stats.json