Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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
  • #6

Closed
Open
Created Nov 14, 2004 by weasel (Peter Palfrader)@weasel

Confused server clocks can screw up timing

[Moved from bugzilla] Reporter: nickm@alum.mit.edu (Nick Mathewson) Description: Opened: 2003-08-29 20:44

Some users have reported that the mixminion server has a nasty failure mode when a server's clock moves backwards by a large interval. When the server asks "when did we last (do something)", the answer "tomorrow" can cause crashes or weird behavior.

I'm deferring this for a while, because (a) I want to get 0.0.5 put to bed, and (b) the workaround is trivial: keep your clock set right.

[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