Opened 7 years ago

Last modified 2 years ago

#7789 new defect

Also display configuration file (torrc) location when running as Windows service

Reported by: mosesofmason Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.4.6-alpha
Severity: Normal Keywords: tor-relay win32 nt-service usability
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When normal running TOR on Windows, it prompts the reading configuration file location such as

Dec 23 05:31:11.523 [notice] Read configuration file "C:\Users\<USERNAME>\AppData\Roaming\tor\torrc".

But TOR does not prompt this location when running as Windows Service, and the torrc file is usually in a totally different location when running as service. TOR just prompt this service is started in command line.

D:\tor>tor --service start

Service started successfully

so it is hard to find which torrc file it is reading. Need a fix on this issue to make it a litter easier.

Child Tickets

Change History (7)

comment:1 Changed 7 years ago by nickm

Keywords: tor-client added

That's going to be a little tricky; once the service starts, I don't think it *has* a stdout to write anything to. We could try to print where we *think* the service will read from, but the service might decide to read from someplace else.

(What do other services do here to pass information back when they're started? Our service interface was made without much knowledge of common conventions in service interfaces.)

comment:2 Changed 7 years ago by mosesofmason

Maybe add a command line parameter option write to a .log file or use the Windows System Log is a good idea?

comment:3 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:4 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 2 years ago by nickm

Keywords: tor-relay win32 nt-service usability added; tor-client removed
Priority: MediumLow
Severity: Normal
Note: See TracTickets for help on using tickets.