Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Monday 24 May 2004 14:04, Nicolas Jungers wrote: > On Mon, 2004-05-24 at 13:54, Philipp Reisner wrote: > > On Monday 24 May 2004 12:28, Bernd Schubert wrote: > > > > you have the choice. if you configure it, it will do things > > > > differently. give it inittimeout=-90 and blame heartbeat if it > > > > decides to make the outdated node primary. > > > > > > I really would prefer if there would be an option not to connect at > > > all, so that after the timeout the drbd devices would become > > > disconnected and the drbd module would be unloaded. In this case > > > heartbeat could be started from a script which checks for the existence > > > of drbd and only starts heartbeat if drbd is available. > > > Currently one has the choice between possible data loss or being unable > > > to do remote administration, IMHO one is as bad as the other. > > > > Currently you also have the choice to do it right :) > > > > E.g. like this: > > [snip] > > > On my systems drbd is started _after_ ssh and heartebat is started > > _after_ drbd. > > > > So where is the problem ? > > the problem is whatever should be started after drbd will be stuck. The > problem is drbd is assuming being the only thing worthy on the box. > Bernd's solution has all my favour. > This is why DRBD's start priority is 70. Usually you have nothing expect heartbeat with a start priority greater than 70. Any may I kindly ask you to get yourself informed about the available options ? Look for "load-only" "skip-wait" and negative init timeouts. Thanks. -philipp -- : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :