User  |  Syst  |  Libr  |  Device  |  Files  |  Other  |  Admin  |  Head  |

---

   pkgtorrent-service    ( 8 )

---

---

Имя (Name)

pkgtorrent-service(8) Is a python WSGI web application that can generate BitTorrent files for binary files available from the web server.

---

Синопсис (Synopsis)

The program should installed on a site local yum mirror and must be configured before use. See pkgtorrent-service.conf(5) for more information.

---

Использование (Usage)

The primary use case for this service is implemented in yum-torrent(1).

There is a secondary interface to assist with simple file downloads involving a single path.

---

Примеры (Examples)

$ curl http://example.com/path/to/large/file > file

       can be converted to using BitTorrent with:

              $ curl http://example.com/path/torrent_service/single/path/to/large/file > file.torrent
              $ btclient file.torrent

       Note the repetition of path before the service name, and the
       addition of torrent_service/single to pass control to the single
       path mode.  Simple file mode supports simple globbing, so you can
       specify .../directory/*.foo.  If the path resolves to only one
       file, the multi-file support in the .torrent file is skipped,
       making the downloaded file easier to handle.

---

Входные файлы (Input files)

/var/lib/torrent_service/trackers The service needs to include one or more BitTorrent tracker servers. The format is one "announce" URL per line. Example: http://example.com:6969/announce This text file is scanned each minute for updates.

---

Выходные файлы (Output files)

The service makes extensive use of cache files. The files are relatively small. It is recommended you periodically clean these caches for files not used in the past month or so.

/var/cache/torrent_service/info/input_digest This directory caches info_hashes for the previously requested path digests. These are used with the current list of trackers to generate .torrent files in constant time.

/var/cache/torrent_service/pieces/path/to/file/blocksize Every file within a torrent is represented by a list of SHA1 digests, one for each blocksize of the file. The SHA1 list is expensive to generate. The same binaries may be downloaded in different permutations by different clients. The cache is invalidated if the original file has a different mtime or is a different size.

---

Ошибки (баги) (Bugs)

Single file mode should be called simple.

---