Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2191

Closed (moved)
(moved)
Open
Created Nov 15, 2010 by Robert Ransom@rransom

Send all error-level log messages to controllers

Right now, if:

  • an assertion fails inside Tor,
  • Tor has disabled sending log messages to its controllers, and
  • Tor is not logging directly to syslog or any file descriptors, Tor will crash silently, with no record anywhere of why it crashed. This is especially bad for users of the Tor Browser Bundles and Vidalia Bundles, which are preconfigured to not log to disk.

Tor should:

  • only log error-level messages when a crash is imminent (e.g. in tor_assert),
  • send log messages to all non-callback log sinks before sending them to callbacks, and
  • send error-level log messages to controllers regardless of whether logging to controllers is otherwise disabled (with the disable_control_logging function or a wrapper around it).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking