Skip to content
GitLab
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 329
    • Issues 329
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • 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
  • #19669
Closed
Open
Issue created Jul 13, 2016 by David Fifield@dcf

`log_prefix_` maybe getting weird output from strftime

legacy/trac#19408 (moved) purports to show tor log lines. The date format in them is really strange:

6/13/2016 23:53:24 PM.700
6/13/2016 23:53:26 PM.200
6/14/2016 0:07:45 AM.200
6/14/2016 0:07:45 AM.200

There's a date string followed by a dot and three digits' worth of fractional seconds. The format doesn't match what's specified in log_prefix_, which is "%b %d %H:%M:%S". https://gitweb.torproject.org/tor.git/tree/src/common/log.c?id=tor-0.2.7.6#n221

I don't see how this can happen, but I thought some one in core tor might want to take a look. Maybe the user has some kind of smart copy-paste that's mangling dates.

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