I am generating a CSV file with the first 2 columns in the Epoch time format.

Here is some sample code:

#!/usr/bin/perl -w 
use strict;
use Data::Dumper;
my $line=<DATA>;

chomp $line;

my @f=split(',',$line);

my $dt1=shift @f;
my $dt2=shift @f;

printf "%s,%s,%s\n",scalar localtime($dt1),scalar localtime($dt2),join
+(",",@f);

exit(0);

__END__
1345752662, 1345752673, CLOSED, CRITICAL, Other fields etc
[download]

The working part of this really is the scalar localtime part. There are other ways of doing this, but this is a time honored method that works. Brute force, but it works.

Here is what perldoc -f localtime says that is pertinate to your situation:

               If EXPR is omitted, "localtime()" uses the current time
+ (as
               returned by time(3)).

               In scalar context, "localtime()" returns the ctime(3) v
+alue:

                   $now_string = localtime;  # e.g., "Thu Oct 13 04:54
+:34 1994"

               This scalar value is not locale-dependent but is a Perl
               builtin. For GMT instead of local time use the "gmtime"
               builtin.
[download]

Hope this is of some help.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.