[asterisk-bugs] [Asterisk 0013592]: STRFTIME returns incorrect time

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13592 
====================================================================== 
Reported By:                georgy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13592
Category:                   Functions/func_strings
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-30 16:44 CDT
Last Modified:              2008-10-01 09:59 CDT
====================================================================== 
Summary:                    STRFTIME returns incorrect time
Description: 
STRFTIME returns incorrect time.

Examples:

NoOp(${STRFTIME(315532800)});
should print: Jan 1 00:00:00 1080
prints: Tue Jan  1 03:59:52 1980

NoOp(${STRFTIME(1199201430)});
should print: Jan 1 15:30:30 2008
prints: Tue Jan  1 19:30:07 2008

NoOp(${STRFTIME(1199929555)});
should print: Oct 1 01:45:55 2008
prints: Wed Oct  1 05:45:32 2008
====================================================================== 

---------------------------------------------------------------------- 
 (0093015) seanbright (manager) - 2008-10-01 09:59
 http://bugs.digium.com/view.php?id=13592#c93015 
---------------------------------------------------------------------- 
Maybe I am not understanding... by default, asterisk will use
/etc/localtime to convert the epoch passed to STRFTIME to the localtime (if
a tz is not specified).  The reporter is GMT+4, which is in line with the
results he is seeing.  Where exactly is the bug in asterisk? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-01 09:59 seanbright     Note Added: 0093015                          
======================================================================