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
  • #6780

Closed (moved)
(moved)
Open
Created Sep 06, 2012 by Rob Jansen@robgjansen

Config fails with non-existent parent of DataDirectory

When passing the "DataDirectory DIR" option, Tor fails during configuration parsing/validation:

[tor-warn] check_private_dir() Error creating directory ./data/middledata/middle: No such file or directory
[tor-warn] Failed to parse/validate config: Couldn't access/create private data directory "./data/middledata/middle"
[tor-err] tor_init() Reading config failed--see warnings above.

In this case data/ existed, but middledata/ (and therefore middledata/middle/) did not. Does it make sense to have check_private_dir() create the parent directories too, like 'mkdir -p'?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking