Still wrote:
* Konnichiwa Guilherme Rocha-sama:
Thank's
Funfou direitinho.
Se vc tiver conex�o 24h com a Net, vc pode atualizar o rel�gio da sua Bios com o ntp, ou seja, seu comp. vai ficar sempre com a hora sempre precisa. Segue o que eu fiz aqui:
-- Script --
#!/bin/bash /usr/sbin/ntpdate -b time.handhelds.org /sbin/hwclock -w
-- Script --
Basta salvar como arquivo.sh e colocar no crontab do root ou do sistema. Aqui eu rodo de 1 em 1 hora.
N�o fa�a isso!
O ideal � vc usar o ntp pra tomar conta do seu rel�gio, ainda mais se vc tiver v�rios micros ligados em rede (o sincronismo � importante).
Nem � t�o dificil assim configur�-lo, e o uso de rede � bem baixo.
Is using ntpdate appropriate - vs ntpd?
The ntpd daemon will adjust the clock slowly, so that the system is not altered. However, the ntpdate command will adjust time suddenly if the error is bigger than 128ms. If the clock jump some seconds strange, or even bad, things can occur. Therefore, ntpd is safer - but we may not have a permanent network connection, and synchronization can take hours. Setting the clock fast is something usually done during computer initialisation (booting up) so that the daemon has an easier job.
However, if we don't have a permanent network connection, using ntpdate is our only way - possibly using the -B parameter, which will force it to slew instead of step the clock.
-- Marcos
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
