[43683] in North American Network Operators' Group
Re: Unix Timestamp
daemon@ATHENA.MIT.EDU (Greg A. Woods)
Mon Oct 22 20:46:37 2001
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: woods@weird.com (Greg A. Woods)
To: nanog@merit.edu
In-Reply-To: <20011022181841.D31965@HiWAAY.net>
Reply-To: nanog@merit.edu (North America Network Operators Group Mailing List)
Message-Id: <20011023004525.A08B2E8@proven.weird.com>
Date: Mon, 22 Oct 2001 20:45:25 -0400 (EDT)
Errors-To: owner-nanog-outgoing@merit.edu
[ On Monday, October 22, 2001 at 18:18:41 (-0500), Chris Adams wrote: ]
> Subject: Re: Unix Timestamp
>
> On Red Hat Linux 7.1:
> $ date -r 1003723200
> date: 1003723200: No such file or directory
The first two were kinda sad examples of the state of commercial Unix
(unfortunately even SuSv2 lacks this now ancient feature!), but this
last one (i.e. GNU date) surprises the heck out of me -- especially
since there's not even an equivalent option with a different name....
> But perl works on all three. :-)
So does the gawk variant, and so would a silly one-line C program. No
doubt python and ruby variants would be equally portable. I really hate
perl. It is the worst of all the bad interpreted languages. Well maybe
not as bad as VB....
But enough of this nonsense -- the best answer is the one from Michael
Barrow to just use FROM_UNIXTIME() in the MySQL code directly.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <gwoods@acm.org> <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
