>>> Kostiantyn Ponomarenko <konstantin.ponomare...@gmail.com> schrieb am >>> 24.07.2015 um 10:45 in Nachricht <caenth0dfwh_ac26axl4icdqxriaz6b3xokoz79zruv+ck31...@mail.gmail.com>: > The idea is to have NTP daemon syncing time right after boot, while > the cluster software starts automatically also at the boot time. > So, there is a slight possibilities that the time will be changed after the > cluster has been started.
25 years backwards? > That is my concern. > > Thank you, > Kostya > > On Fri, Jul 24, 2015 at 8:56 AM, Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> >>> Kostiantyn Ponomarenko <konstantin.ponomare...@gmail.com> schrieb am >> 23.07.2015 >> um 18:09 in Nachricht >> <caenth0ekjv8udjp5gobjpp8yovzrct_xsuv7gn93toppalc...@mail.gmail.com>: >> > Hi, >> > >> > If you do: >> > # date --set="1990-01-01 01:00:00" >> >> Why would you do that in a running cluster? >> >> > when only one node is present in the cluster and while the cluster is >> > working, and then stop a resource (any resource), the cluster fails the >> > resource once, shows it as Started, but the resource actually is still >> > stopped. >> > >> > Is it the expected behavior in the cluster? >> > Is it prohibited to change time/date while the cluster is working? >> > >> > The environment: two node cluster with just one node up; pacemaker >> 1.1.12. >> > >> > Thank you, >> > Kostya >> >> >> >> >> >> _______________________________________________ >> Users mailing list: Users@clusterlabs.org >> http://clusterlabs.org/mailman/listinfo/users >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
