1 |
Hi, |
2 |
Those dates are in a format called "unix timestamps", which represent |
3 |
the number of seconds since the unix epoch (Jaunuary 1st, 1970). You |
4 |
can get the current unix timestamp via the date command (date +%s). As |
5 |
far as any command-line utility to convert them,I leave that to |
6 |
Google. However, most programming languages provide functions to |
7 |
convert between timestamp formats. |
8 |
|
9 |
-- Greg |
10 |
|
11 |
On Jan 27, 2008 4:54 PM, Mick <michaelkintzios@×××××.com> wrote: |
12 |
> Hi All, |
13 |
> |
14 |
> I am sure that someone has asked this before, but a cursory look doesn't bring |
15 |
> anything up. I am going through some logs and I cannot understand what the |
16 |
> time was when certain events took place: |
17 |
> |
18 |
> [1200806556] SERVICE ALERT: router.xxxxxxxxxxxxxxxxxxxxxxx |
19 |
> [1200806576] SERVICE ALERT: router.xxxxxxxxxxxxxxxxxxxxxxx |
20 |
> [1200806891] HOST ALERT: router.xxxxxxxxxxxxxxxxxxxxxxxxxx |
21 |
> [1200806891] |
22 |
> |
23 |
> Could you please tell me how to interpret/parse these so that they show time |
24 |
> in hrs:min so that I can understand it? (anything I could feed to less would |
25 |
> be grand). |
26 |
> -- |
27 |
> Regards, |
28 |
> Mick |
29 |
> |
30 |
-- |
31 |
gentoo-user@l.g.o mailing list |