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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Jun 05, 2015 by Karsten Loesing@karsten

Implement lock file in a more robust way

The current lock file gets written when the hourly updater starts and gets deleted when it exits. It's really good in preventing concurrent executions. But it doesn't handle cases when a process doesn't exit cleanly, because subsequent executions won't start at all. One possibility for not exiting cleanly is that the machine gets rebooted while the hourly updater is running.

One way to fix this might be to use Java's FileLock instead of making up our own lock file.

This is more a defect than an enhancement, because it broke the main Onionoo service instance.

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