in reply to TIME::LOCAL problem - repost with better info

Can you post a link to your earlier troubleshooting attempts on perlmonks or elsewhere?

What version of time::local are you using?

Did you try make test on it?

Can you make a script that will duplicate the problem, for your system as it is running *now*?

Can you include comments, and format the output to be more understandable for those not familiar with time::local? As it stands now, it's not really clear why your "bad" output is bad to me.

Can you solve the whole problem by using one of the other time oriented modules, like localtime?

Good luck.

  • Comment on Re: TIME::LOCAL problem - repost with better info

Replies are listed 'Best First'.
Re^2: TIME::LOCAL problem - repost with better info
by Anonymous Monk on May 19, 2005 at 14:25 UTC
    Answers:

    First post was http://www.perlmonks.com/?node_id=454853

    As included in the post Time::Local is 1.07
    Production box with HP supplied perl. Did not compile perl on this device.

    The code listed is the actual code running. The only change from production was to print the values to document the problem.

    Time::Local takes the six parameters listed in the output as values sent and returns date & time in number of seconds. Return value from time local is the number of seconds returned from each time::local call. All dates are within five years of each other so returned values should be within around 157680000 seconds of each other (5 years worth of seconds). The difference between the first bad return value and the data prior is 994114800 seconds.

    Due to business requirements, I can only use modules included from HP.
    thanks
[reply]
      Do these business requirements mean you can't upgrade to the latest Time::Local version -- 1.11? Might be worth a shot.
[reply]

In Section Seekers of Perl Wisdom