the man page for ntp is fairly description and the internet is full of ntp instructions, how-tos, etc. the ntpd demon can be stopped and started by hand and does not require a reboot. the applications should not notice it; they typically use whatever time is given when they request the time. the issue that you may face is that your different servers have different times. this may or may not be an issue. (it was a one place that i have worked.) the date command can be use to explicitly change the time on a server. the man page gives the details. both the date command and the ntpd process don't disrupt properly functioning servers. both require minimal resources. On Thu, Nov 19, 2009 at 3:08 AM, Esteban Torres Rodriguez <etorres@xxxxxx>wrote: > Hello, > > I have many servers when I'm wrong and my server configured with ntp. > These are production servers that can not stop and not what is the best > procedure to change the time. > > Those who have delayed the advance time without problems but when I have > to give back as no how. > > Servers are Oracle, MySQL, Apache, OAS, etc. .... > > "As you do? > What procedure you use? > > -- > ################################################## > # Esteban Torres Rodríguez # > # Área de Soporte Técnico # > # Subdirección de Sistemas Informáticos # > # Empresa Pública Desarrollo Agrario y Pesquero # > # email: etorres@xxxxxx # > ################################################## > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
