Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Oh oh... Effectively I'm wrong, the trailing "sed s/255/0/" in the accompanying command list speaks by itself... Those commands were sounding so bulky when I read that doc some months ago that I mistakenly interpreted the sequence in my own way to do things manually by myself as usual (I'm from the old school...), so my config files are wrong now. William, sorry for having been misleading, and thanks Arnold to point that out. The cool thing (to me) is that I learn something more everyday on this ML... Best regards, Pascal. -----Message d'origine----- De : drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] De la part de Arnold Krille Envoyé : jeudi 7 juin 2012 21:02 À : drbd-user at lists.linbit.com Objet : Re: [DRBD-user] Corosync Configuration On 07.06.2012 19:28, Pascal BERTON wrote: > I also used this manual to startup, I agree with Jake, that's a typo. Apart from that, William, your "bindnetaddr" parameter should not end with a "0", it's supposed to be the IP address your local host/node will use to monitor its peers. Instead, replace it by the IP address your server has on network 192.168.1.0. Please read the name as what it is: bindnetaddr = bind to net with the (network)-address. So, yes writing 0 as the last part (in our networks its the last two parts) is correct. Corosync determines the interface from the connected network. And writing it in this way in the config allows to have the very same config file on all hosts taking part in the cluster. Have fun, Arnold -- Dieses Email wurde elektronisch erstellt und ist ohne handschriftliche Unterschrift gültig.