-
-
Notifications
You must be signed in to change notification settings - Fork 447
LOG Logging
Jari Sundell edited this page Oct 24, 2025
·
6 revisions
# 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.
# 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.
"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