Ticket 155 - RFC 2822 compliant timestamps
Summary: RFC 2822 compliant timestamps
Status: RESOLVED FIXED
Alias: None
Product: Slurm
Classification: Unclassified
Component: Other (show other tickets)
Version: 2.5.x
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Moe Jette
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2012-11-05 23:00 MST by Janne Blomqvist
Modified: 2012-11-06 03:43 MST (History)
1 user (show)

See Also:
Site: -Other-
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Patch for RFC 2822 compliant timestamps (2.30 KB, patch)
2012-11-05 23:00 MST, Janne Blomqvist 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Janne Blomqvist 2012-11-05 23:00:27 MST 
Created attachment 147 [details]
Patch for RFC 2822 compliant timestamps

Hi,

I'm investigating some weirdness with time calculations, and stumbled upon the following minor bug; namely that the RFC 822 timestamps that slurm sometimes uses conform to neither RFC 822 or RFC 2822 (the current version which supersedes 822). The attached patch fixes it to conform to RFC 2822.
Comment 1 Danny Auble 2012-11-06 03:43:27 MST 
Thanks Janne, this has been added to 2.5.

3ca6f99ce2478584a5275a400e5b843163a538a4