Denis Shaposhnikov

Is it possible that's because every torrent has a LAN local tracker? Like this: ``` http://bt3.t-ru.org/ann http://retracker.local/announce ``` From this example `retracker.local` doesn't exists, because I don't have any retracker...

> there must only one tracker in the list I tried it and unfortunately it doesn't work. I removed `retracker.local` from all of my torrents and today one of torrents...

Yes, after restarting transmission daemon tremotesf reports `Errored (1)` as expected. I'd like to note, transgui reports not registered torrents even without transmission daemon restart.

Hi! Any news on that?

> client: zrepl version=v0.6.1 go=go1.21.12 GOOS=freebsd GOARCH=amd64 Compiler=gc server: zrepl version=v0.6.1 go=go1.21.12 GOOS=freebsd GOARCH=amd64 Compiler=gc I'd suggest you try `sysutils/zrepl-dsh2dsh`. It has many improvements and it's in the FreeBSD ports...

JFYI, in my [fork](https://github.com/dsh2dsh/zrepl) I implemented a timeout and it helped me a lot. Also, using a cron spec I configured some jobs with same ZFS datasets, so zrepl fires...

> On the system in question, only 25 file systems are managed by zrepl Are they all under the same root? So for your case `zfs list -H -p -o...

@guest20 @trekzavier Hi, if you need rate limits, feel free to try my fork https://github.com/dsh2dsh/miniflux where I implemented rate limits and some more features.

@guest20 > Any reason your rate limits can't be put into a PR? No reason, just not my goal. Anybody feel free to backport it.

@guest20 Correct. `RATE_LIMIT_PER_SERVER=1` is one connection per server per second.