mirror of
https://github.com/rakshasa/rtorrent.git
synced 2026-08-05 17:52:29 +00:00
Page:
LOG Logging
Pages
Android App
Auto Scraping
CLI Usage
COMMAND Conditional
COMMAND Conversions
COMMAND Execute
COMMAND Scheduling
COMMAND System
COMMAND UserInterface
CONFIG Template
Choke Groups
Command‐Reference‐Complete
Config Guide
Daemon_Mode
Docker
Favoring group of torrents
Home
IP filtering
Installing
Issues
LOG Logging
Lua‐Configuration
Parentheses and Braces Syntax
Performance Tuning
Protocol Encryption Configuration
Proxy Configuration
RPC Migration 0.9
RPC Option Strings
RPC Setup XMLRPC
RPC Utility XMLRPC2SCGI
RTorrentRatioHandling
Scripting Guide
Socket Manager and Resource Allocation
TODO
TORRENT Watch directories
Tor based Proxying Guide
User Guide
Vagrant
rTorrent 0.9 Comprehensive Command list (WIP)
Clone
7
LOG Logging
Jari Sundell edited this page 2026-04-20 01:11:39 +09:00
Logging
Opening Log Files
# log.open_file = "log name", "file path"
log.open_file = "rtorrent.log", (cat,/tmp/rtorrent.log.,(system.pid))
A newly opened log file is not connected to any logging events.
Some control over formatting will be provided at a later date.
Adding outputs to events
# log.add_output = "logging event", "log name"
log.add_output = "info", "rtorrent.log"
log.add_output = "dht_all", "tracker.log"
log.add_output = "tracker_events", "tracker.log"
log.add_output = "tracker_requests", "tracker.log"
Each log handle can be added to multiple different logging events.
Special Commands for Early Logging
#
# do:log.open_file=system,/Users/rakshasa/torrent/host/logs/system.log
# do:log.open_file=rtorrent,/Users/rakshasa/torrent/host/logs/rtorrent.log
#
# do:log.add_output=system,system
# do:log.add_output=debug,rtorrent
#
log.open_file = "crash", /Users/rakshasa/torrent/host/logs/crash.log
log.add_output = "critical", "crash"
Above is an example rtorrent.rc file that adds logging outputs before normal initialization and reading of config files.
It handles any # do: prefix as special commands, and is limited and has strict syntax requirements.
Logging events
"critical"
"error"
"warn"
"notice"
"info"
"debug"
The above events receive logging events from all the sub-groups displayed below, and each event also receives events from the event above in importance.
Thus some high-volume sub-group events such as “tracker_debug” are not part of “debug” and every “warn” event will receive events from “error”, “critical”.
critical
error
warn
notice
info
debug
peer_critical
peer_error
peer_warn
peer_notice
peer_info
peer_debug
socket_critical
socket_error
socket_warn
socket_notice
socket_info
socket_debug
storage_critical
storage_error
storage_warn
storage_notice
storage_info
storage_debug
thread_critical
thread_error
thread_warn
thread_notice
thread_info
thread_debug
torrent_critical
torrent_error
torrent_warn
torrent_notice
torrent_info
torrent_debug
connection
connection_bind
connection_fd
connection_filter
connection_hanshake
connection_listen
dht
dht_all
dht_error
dht_controller
dht_node
dht_router
dht_server
instrumentation_memory
instrumentation_mincore
instrumentation_choke
instrumentation_polling
instrumentation_transfers
mock_calls
net_dns
peer_list_events
peer_list_address
protocol_piece_events
protocol_metadata_events
protocol_network_errors
protocol_storage_errors
resume_data
rpc_events
rpc_dump
storage
system
tracker_dump
tracker_events
tracker_requests
ui_events