-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Are there any warnings in the kernel messages about your clock? A possible "solution" would be running a "ntpd" server (not using the client, but the server). It *should* adjust your clock in stages to maintain the correct time ~ unnoticiably ;-) I read about this solution somewhere on the internet. Apparently it calculates the adjustments needed (based on difference in time of your hardware and the real time), and every few minutes adds/removes the needed seconds to your time. This also saves you from adjusting time smoothly (like in your case 30 minutes) without having errors from running services who use/need time.
Greetings Ralph Antonio Coralles wrote: > I've a strange problem: The clock of my computer ticks to fast - i get > an error of about 30 minutes per day ... > This problem just occured recently - a few days ago everthing was ok, > possibly before 'emerge -up --deep world' ... > Maybe someone can give me a hint. > Thanks > antonio > -- > [email protected] mailing list > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCSVRyAWKxH5yWMT8RAttWAKChy7OMH+5cgbVHPns2yNfPcvkUyACff1X3 eIvUWKYGUo3ahkVMTkAEeDk= =h0ze -----END PGP SIGNATURE----- -- [email protected] mailing list
