Re: Decode unixtime

2010-01-27 Thread Osamu Aoki
Hi, On Tue, Jan 26, 2010 at 07:39:09PM -0500, Celejar wrote: On Fri, 15 Jan 2010 16:18:31 -0500 Chris Jones cjns1...@gmail.com wrote: On Fri, Jan 15, 2010 at 09:29:04AM EST, Celejar wrote: On Fri, 15 Jan 2010 03:56:11 -0500 Chris Jones cjns1...@gmail.com wrote: [..] bash info still

Re: Decode unixtime

2010-01-27 Thread Celejar
On Wed, 27 Jan 2010 22:05:02 +0900 Osamu Aoki os...@debian.org wrote: Hi, On Tue, Jan 26, 2010 at 07:39:09PM -0500, Celejar wrote: On Fri, 15 Jan 2010 16:18:31 -0500 Chris Jones cjns1...@gmail.com wrote: On Fri, Jan 15, 2010 at 09:29:04AM EST, Celejar wrote: On Fri, 15 Jan 2010

Re: Decode unixtime

2010-01-27 Thread Stephen Powell
On Wed, 27 Jan 2010 08:53:18 -0500, Celejar wrote: What I meant was that I see no definitive answer to the general semantic question of whether stuff in the non-free section is 'in Debian' or not. Excuse me for butting in here, gentlemen, but perhaps these links will help clarify things:

Re: Decode unixtime

2010-01-27 Thread Celejar
On Wed, 27 Jan 2010 09:19:19 -0500 (EST) Stephen Powell zlinux...@wowway.com wrote: On Wed, 27 Jan 2010 08:53:18 -0500, Celejar wrote: What I meant was that I see no definitive answer to the general semantic question of whether stuff in the non-free section is 'in Debian' or not. Excuse

Re: Decode unixtime

2010-01-27 Thread Stephen Powell
On Wed, 27 Jan 2010 14:54:21 -0500, Celejar wrote: So IIUC, the first link indicates that non-free is indeed still part of Debian, at least in some sense. I am not an official spokesman for Debian, but it would appear so, yes. This was an official vote, it passed by a large margin, and as far

Re: Decode unixtime

2010-01-26 Thread Celejar
On Fri, 15 Jan 2010 16:18:31 -0500 Chris Jones cjns1...@gmail.com wrote: On Fri, Jan 15, 2010 at 09:29:04AM EST, Celejar wrote: On Fri, 15 Jan 2010 03:56:11 -0500 Chris Jones cjns1...@gmail.com wrote: [..] it's generally available in non-free - no need to do anything manually.

Re: Decode unixtime

2010-01-19 Thread T o n g
On Sat, 16 Jan 2010 21:31:19 +, Clive Standbridge wrote: How about date -I date -Iseconds Sortable, readable, parseable and standard to boot. Using Lenny? -- the '-I' will be gone soon. It is not even in Squeeze's man page now. -- Tong (remove underscore(s) to reply)

Re: Decode unixtime

2010-01-19 Thread John Hasler
Tong writes: the '-I' will be gone soon. It is not even in Squeeze's man page now. Still works in version 8.4 in Sid, though. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Re: Decode unixtime

2010-01-19 Thread Clive Standbridge
Using Lenny? -- the '-I' will be gone soon. It is not even in Squeeze's man page now. Yes lenny, it's disappeared from the man page already, and in fact it's not in etch's man page either. I wasn't aware of this bug but it has been reported 4 years ago!

Re: Decode unixtime

2010-01-19 Thread Chris Davies
On 20100115_051059, T o n g wrote: Which tool can help me decode the Unix time? E.g., strings like 1257624539, 1258162046, 1257623988, 1257709563, etc. [...] Alex Samad a...@samad.com.au wrote: I believe squid logs like that ! That's correct. The squid FAQ also gives a perl snippet to

Re: Decode unixtime

2010-01-16 Thread Brian Ryans
Quoting Paul E Condon on 2010-01-15 01:09:33: I suggest that you change the way you get the numbers so that they are both human readable and parsable by simple code. I like date +%Y%m%d_%H%M%S +%F_%T is what I use when spaces aren't desirable in dates. See my quoting line for a slightly

Re: Decode unixtime

2010-01-16 Thread Brian Ryans
Quoting Chris Jones on 2010-01-15 02:56:11: behaves a bit more like a text-mode web browser. pinfo's maintainer would agree with you. Quoting 'apt-cache show pinfo': Description: An alternative info-file viewer pinfo is an viewer for Info documents, which is based on ncurses. The key-commands

Re: Re: Decode unixtime

2010-01-16 Thread Clive Standbridge
I suggest that you change the way you get the numbers so that they are both human readable and parsable by simple code. I like date +%Y%m%d_%H%M%S +%F_%T is what I use when spaces aren't desirable in dates. See my quoting line for a slightly modified example of it. From my experience,

Re: Re: Decode unixtime

2010-01-16 Thread Brian Ryans
Quoting Clive Standbridge on 2010-01-16 15:31:19: How about date -I date -Iseconds Sortable, readable, parseable and standard to boot. Wow, thanks for that Clive. Easier to remember, too. I just tried it in a shell one-liner, and I used a bit less logic to parse it than other

Re: Decode unixtime

2010-01-16 Thread Chris Jones
On Fri, Jan 15, 2010 at 11:32:30PM EST, Brian Ryans wrote: Quoting Chris Jones on 2010-01-15 02:56:11: behaves a bit more like a text-mode web browser. pinfo's maintainer would agree with you. Quoting 'apt-cache show pinfo': Description: An alternative info-file viewer pinfo is an viewer

Re: Decode unixtime

2010-01-15 Thread Teemu Likonen
On 2010-01-15 05:20 (UTC), Chris Jackson wrote: It's not well documented, but: date -d, with an '@' before it: chr...@hercule$ date -d '@1257624539' Sat Nov 7 20:08:59 GMT 2009 It's documented quite well in info pages, though: $ info coreutils date inv $ info coreutils seconds (Or

Re: Decode unixtime

2010-01-15 Thread Chris Jones
On Fri, Jan 15, 2010 at 02:46:07AM EST, Teemu Likonen wrote: On 2010-01-15 05:20 (UTC), Chris Jackson wrote: It's not well documented, but: date -d, with an '@' before it: chr...@hercule$ date -d '@1257624539' Sat Nov 7 20:08:59 GMT 2009 It's documented quite well in info pages,

Re: Decode unixtime

2010-01-15 Thread Celejar
On Fri, 15 Jan 2010 03:56:11 -0500 Chris Jones cjns1...@gmail.com wrote: ... Besides, I hear that due to licensing restrictions, some of the info pages are not available from the debian repos. As a result, if you don't mind tainting your debian system, you need to download them from the GNU

Re: Decode unixtime

2010-01-15 Thread Chris Jones
On Fri, Jan 15, 2010 at 09:29:04AM EST, Celejar wrote: On Fri, 15 Jan 2010 03:56:11 -0500 Chris Jones cjns1...@gmail.com wrote: [..] it's generally available in non-free - no need to do anything manually. Maybe this has changed, but on lenny, I vaguely remember installing the bash and

Decode unixtime

2010-01-14 Thread T o n g
Hi, Which tool can help me decode the Unix time? E.g., strings like 1257624539, 1258162046, 1257623988, 1257709563, etc. they are about 68 days ago. Thanks -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ -- To UNSUBSCRIBE,

Re: Decode unixtime

2010-01-14 Thread Chris Jackson
T o n g wrote: Hi, Which tool can help me decode the Unix time? E.g., strings like 1257624539, 1258162046, 1257623988, 1257709563, etc. they are about 68 days ago. Thanks It's not well documented, but: date -d, with an '@' before it: chr...@hercule$ date -d '@1257624539' Sat Nov 7

Re: Decode unixtime

2010-01-14 Thread Paul E Condon
On 20100115_051059, T o n g wrote: Hi, Which tool can help me decode the Unix time? E.g., strings like 1257624539, 1258162046, 1257623988, 1257709563, etc. they are about 68 days ago. Thanks date contains the standard time/date handling code, but it is inconvenient to give it a ten

Re: Decode unixtime

2010-01-14 Thread Alex Samad
On Fri, Jan 15, 2010 at 12:09:33AM -0700, Paul E Condon wrote: On 20100115_051059, T o n g wrote: Hi, Which tool can help me decode the Unix time? E.g., strings like 1257624539, 1258162046, 1257623988, 1257709563, etc. they are about 68 days ago. Thanks date contains the

Re: Decode unixtime

2010-01-14 Thread Kun Niu
Have you tried the function ctime? Alex Samad wrote: On Fri, Jan 15, 2010 at 12:09:33AM -0700, Paul E Condon wrote: On 20100115_051059, T o n g wrote: Hi, Which tool can help me decode the Unix time? E.g., strings like 1257624539, 1258162046, 1257623988, 1257709563, etc. they are