OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Michal Jaegermann (michalellpspace.math.ualberta.ca)
Date: Tue Mar 26 2002 - 10:03:17 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Thu, Jan 01, 2015 at 11:05:23AM -0700, Thursday AKA dr. john wrote:
    >
    > I wonder how the two bioses could have got out of sync like that?

    They are not "out of sync". They just interpret "raw numbers" provided
    by hardware in a different way. :-)

    At least in Linux 'hwclock' command has various options which affect
    how hardware data are interpreted. See 'man hwclock' for gory details.
    Due to various hardware clocks (there is more than two even if this
    sounds strange) this does not always work. If an offset is constant
    you may manipulate your system clock in startup scripts; that means,
    if you insist on running billgware which will whack your clock every
    time. Something like that, but this is kind of gross:

      if [ "$(date %Y)" -ge $crazy_value ] ; then
          date --set='-20 years'
      fi

    Take care about doing that early enough or you will get complaints
    about weird time-stamps in various places.

      Michal

    _______________________________________________
    Axp-list mailing list
    Axp-listredhat.com
    https://listman.redhat.com/mailman/listinfo/axp-list