Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 315
    • Issues 315
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #387
Closed
Open
Created Feb 08, 2007 by seeess@seeess

old v1 directories never get expired

On our priv network we only run v2 dirs / clients, but we used to run v1 and not all OR's updated at the same time causing it ti still cache all the old v1 directories. So we still have directories that are from December cached and can not get rid of them without taking down every OR in the network. I'd be nice to have a rejectv1dirs option but I realize that's a niche option, so I'd also be happy with them expiring after a month or so. Apparently this already happens for v2 directories.

currently still publishing old v1 directories. "published 2006-12-30 17:08:49"

also "reported version" on this flyspray tracker needs to be updated to 0.1.2.7-alpha

[Automatically added by flyspray2trac: Operating System: All]

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