🚀 go-pugleaf

In article <davison.716941195@sfu.ca> davison@selkirk.sfu.ca (R. Davison) writes:
>marra@samuel.enet.dec.com (Dave Marra) writes:
>
>>re: talk about moving the system clock back.
>
>>Why can't the license system keep an internal timestamp inside it's license
>>database somewhere, and then, when it detects that time has taken a step
>>backwards, simply disable all licenses?  
>
>The clock on our systems needs to adjusted occassionally.  If I had to
>reinstall all licenced systems every time, I'd be wishing for a better 
>scheme.  Licencing, should not inconvenience legitimate users.
>
>>At that point it would take a complete re-installation of the entire license
>>system, including the licenses to get everything back online.  I would think
>>that would deter folks from setting the clock back.
>
>Rod  Davison.
>

	Another method used by licensing software to assure date validity is
    by checking the creation dates of certain files in the /etc directory...
    This is a much safer method than utilizing an internal timestamp, IMHO.

         ~ deej ~              | (If I were expressing Cadence's opinions, )
Jim Howard -- deej@cadence.com | (they'd probably make me wear a tie...    )
        (^:=             Flames cheerfully ignored.             =:^)
"I used to be disgusted, but now I'm just amused..." -- Elvis Costello