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

Closed (moved)
Open
Opened Apr 16, 2012 by cypherpunks@cypherpunks

Clock syncing feature

Some people run Tor relays on virtual servers. Sadly sometimes those servers' clocks are incorrect or jumping like crazy. And as we all know, having an accurate clock is important for a Tor relay.

The problem is that a clock can't be accessed or modified by user, even as root.

So I got an idea. Perhaps there should be a feature so Tor could sync the time on its own - for itself - without requiring root access or anything.

Perhaps it could a torrc line called NTPSyncServer or something

NTPSyncServer ntp.ubuntu.com

TorTimezone GMT+5

If implementing ntp support is a bad idea, some kind of clock syncing feature would be really nice.

To upload designs, you'll need to enable LFS and have 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#5633