Provided by: fake-hwclock_0.5_all bug


       fake-hwclock - Control fake hardware clock


       fake-hwclock [ command ] [ force ]


       Many  embedded  Linux  systems do not have a functional hardware clock. Either they simply
       don't have a hardware clock at all or they have a hardware clock  but  it  is  not  usable
       (e.g. because Linux doesn't know how to use it or because no battery is present).

       This  can lead to time moving backwards to some default value (often 1970) when the system
       is rebooted. Since lots of software assumes that time only moves forward  this  is  a  bad
       thing.  NTP  can  (and should where practical) be used to sync with an external timeserver
       but it is not available early in the  boot  process  and  may  be  unavailable  for  other


       fake-hwclock  sets  and  queries  a fake "hardware clock" which stores the time in a file.
       This program may be run by the system administrator directly but is typically run by  init
       (to load the time on startup and save it on shutdown) and cron (to save the time hourly).

       If no command is given then fake-hwclock acts as if the save command was used.


       save   Save the time to the file.

       load   Load the time from the file. If force is specified fake-hwclock will move the clock
              either backwards or forwards. Otherwise it will only move it forwards.


              The file used to store the time

              The init script used to run fake-hwclock on startup and shutdown

              Settings file for the init script.

              Cron job used to save the time hourly


       FILE   set the file used by fake-hwclock


       1 is returned for invalid commands. 0 is returned in all other cases.


       This approach can only provide a  crude  approximation  of  what  a  real  hardware  clock
       provides. Use of NTP or another method to keep the time in sync is strongly advised.