Compare commits

..

No commits in common. "e199b999473d82a1b5e06d84415c228451d8425e" and "df53667f91c4674dadc2daf5bfb5ccb96498a18f" have entirely different histories.

3 changed files with 3 additions and 32 deletions

View File

@ -124,7 +124,7 @@ Refreshing keys will tell you if some key you have contains a signature from som
gpg --refresh-keys gpg --refresh-keys
``` ```
You can use the [crontab](../../basics/cron.md) to refresh keys. You can use the [crontab](../basics/cron.md) to refresh keys.
# Export # Export

View File

@ -1,6 +1,6 @@
--- ---
title: "Void locale" title: "locales"
tags: [ "void", "locale" ] tags: [ "void" ]
--- ---
Check the current locales: Check the current locales:

View File

@ -136,32 +136,3 @@ Without the `--anonymize` flag, the torrent file output will have a 'created by'
- udp://explodie.org:6969/announce - udp://explodie.org:6969/announce
- https://tracker.gbitt.info:443/announce - https://tracker.gbitt.info:443/announce
- http://tracker.gbitt.info:80/announce - http://tracker.gbitt.info:80/announce
## Verify
Add your torrent and notes its number:
```bash
transmission-remote -a "$file".torrent
transmission-remote -l
transmission-remote -t "$number" -i
```
The information in the last command shows that it's not verified, so you can verify with `-v`.
```bash
transmission-remote -t "$number" -v
```
If transmission cannot find it, then tell it where to find the torrent:
```bash
transmission-remote -t "$number" --find "$(pwd)"
```
...and of course, make sure the permissions allow transmission to see the target.
```bash
ls -ld "$file"
```