Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #4374

Closed (moved)
Open
Opened Nov 01, 2011 by Roger Dingledine@arma

If you explicitly specify a geoip file and it's not there, shouldn't Tor fail?

$ src/or/tor geoipfile /path/not/here

results in this subtle line in my logs

Nov 01 06:47:50.000 [info] geoip_load_file(): Failed to open GEOIP file /path/not/here.

and no other troubles. That's probably not what we expected.

I expect this is messy to fix due to the crazy "" default that we have in config.c.

Bug found by Sebastian.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#4374