Tor for Windows lacks eventlog support
Tor for Windows does not support Windows' native system event logging facility "eventlog". Syslog is unsupported on Windows so an enhancement of Tor for Windows is necessary.
Administrators of Tor relays on Windows have a hard time of keeping track of Tor's events. This enhancement should ease this problem.
Logconfiguration option's value
syslogshould enable logging to eventlog and be synonymous with the new value
eventlogon Windows systems.
- A new
Logconfiguration option value
eventlogshould be added. Setting
eventlogshould enable logging to eventlog on Windows and be synonymous on other operating systems with the
- Eventlog supports only four relevant event types for this matter:
EVENTLOG_SUCCESSusually maps to
EVENTLOG_INFORMATION_TYPEleaving effectively three event types. These event types have to correspond to syslog's priorities/severities. Proposed corresponding:
EVENTLOG_ERROR_TYPEVerbosity should remain unaffected of priority/severity to event type correspondings, e.g.
noticeshould not produce
debugeventlog reports although they all correspond to the same event type
Installing Tor as a service
- When installing Tor as service with "
tor.exe --service install" tor should create an event source in the registry for eventlog.
- When removing the Tor service with "
tor.exe --service remove" the previously created event source during service installation should be removed from registry.
NOTE: Generally speaking, this Tor installing as a service feature should be revised because by convention it is an uncommon practice on Windows for tools to provide such a feature. Service installation functionality is provided by the
sc.exe external command and the Windows Installer (and the PowerShell lately). The preferred way for software vendors to install services is via the Windows Installer during application setup.
Use a cross-platform logging library with good support for Windows.