Problem statement :  Perils of date and timestamp management

                     viz. translating into who,whom,why,How.

                     From a operating system context why should a
                     system admin be provided to manipulate date,timestamp

                     i.e. systemclock ...perils of changing or varying the date
                     or timestamp or running system
 
Opportunity :        

                     Translating into delegation of such authority or previleges ??

                     ....ideally any interface to manipulate CMOS clock

                         or update the processor counters ...cloak cycle counting

                         ....should ideally be disabled

                     similarly ...synchronization of the clock of cloak counters
                     ....over network ..either NTP ....translating into confulence
                     of power at one-point ....resulting into pontentially large
                     scale manipulations ....


                     hence ideally ....a difference of systemclock with those of
                     NTP ...should be ...ideally brought to notice of all the users
                     of the system ...kind of wall broadcast when a system is going
                     down as also the  unix syslog ...management.

              
              
Note: The above problem statement having been encountered in various scenarios
      and detailed in various 'Proof of concepts' as mentioned in 
      'http://uk.geocities.com/ravivenkatus/projects.pdf' ....apply appropriate
      'use-case' modeling, rationalize and arrive at a workable and feasible 
       solution both commercially and techinically viable.

             

           


 
             