Re: vdr 1.3.25 thread problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 1 Jun 2005, Rainer Zocholl (RZ) wrote:

RZ> 
RZ> >the calculated time IS correct. you can use the small tool 'time' from
RZ> >nvram-wakeup package:
RZ> 
RZ> >  # ./time 1117634400
RZ> >  (time_t)     1117634400
RZ> >  (local time) Wed Jun  1 16:00:00 2005
RZ> >  (utc/gmt)    Wed Jun  1 14:00:00 2005
RZ> 
RZ> >or, if you trust 'date', use this:
RZ> 
RZ> >  # date +%s -d "Wed Jun  1 16:00:00 CEST 2005"
RZ> >  1117634400
RZ> 
RZ> 
RZ> I forgot to copy that test done here:
RZ> 
RZ> msi:~/video/nvram/nvram-wakeup# ./time 1117634400
RZ> (time_t)     1117634400
RZ> (local time) Wed Jun  1 16:00:00 2005
RZ> (utc/gmt)    Wed Jun  1 14:00:00 2005
RZ> 
RZ> 
RZ> But why:

try reading documentation on time_t (e.g. in glibc manual)

again, the following commandos _do_not_ convert time_t back to human 
readable format. unfortunately (AFAIK), date has only the way 
humanreadable -> time_t (see example above)

RZ> #  date  -d  "1970-01-01 1117634400 sec CET"
RZ> Wed Jun  1 15:00:00 CEST 2005
RZ> #  date  -d  "1970-01-01 1117634400 sec CEST"
RZ> Wed Jun  1 15:00:00 CEST 2005
RZ> #  date  -d  "1970-01-01 1117634400 sec GMT"
RZ> Wed Jun  1 16:00:00 CEST 2005
RZ> # date  -d   "1970-01-01 1117634400 sec WET"
RZ> Wed Jun  1 16:00:00 CEST 2005


        Sergei
-- 
--------------------------------------------------------------------  -?)
         eMail:       Sergei.Haller@xxxxxxxxxxxxxxxxxxx               /\\
-------------------------------------------------------------------- _\_V
Be careful of reading health books, you might die of a misprint.
                -- Mark Twain


[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux