Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 19 Nov 2004, philipp.reisner at public.gmane.org wrote: > BTW, what do you want to achieve [with the negative timeout] ? The default behaviour is quite dangerous: it can halt the machine by itself  and lock the whole boot process  in case of degraded cluster! I would like DRBD to start as fast as possible at boot time on every nodes (without any timeout or user input) and let Heartbeat or the sysadmin decide whenever one node or the other should become primary or secondary. I don't want DRBD to make cluster-wide decisions because it's (just) a block device driver. At this time and according to the manual, I haven't found a way to make such a configuration properly. Is there a way to tell DRBD not to become primary at boot time and at the same time not to wait for a secondary?  incon-degr-cmd "halt -f";  wfc-timeout 0; -- Cyril Bouthors -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20041122/541874f3/attachment.pgp>