[DRBD-user] Default drbdmanage system-kill behavior

Roland Kammerer roland.kammerer at linbit.com
Fri Nov 3 08:50:27 CET 2017

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Thu, Nov 02, 2017 at 04:52:11PM +0100, Mariusz Mazur wrote:
> 2017-10-30 11:53 GMT+01:00 Robert Altnoeder <robert.altnoeder at linbit.com>:
> 
> Avoiding this very low probability russian roulette is very easy, as
> long as an admin is made aware of it.
> 
> May I suggest putting all this stuff under a single section of the
> documentation and then:
> - mentioning it really early in the "5. Common administrative tasks -
> DRBD Manage" that if you don't take a look at this section and
> configure your system accordingly, you're asking for trouble
> - putting a link at the top of "8. Troubleshooting and error recovery"
> - having 'drbdmanage init' mention it. It's quite chatty already, no
> reason not to have it nag the admin to go through a system config
> checklist.

Sounds very reasonable to me.

> Not a single line of code needs to be written (well, almost) and a lot
> of admin hours might get saved. Hell, I'll do it if the docs have
> sources somewhere public and you confirm that's an acceptable change
> for you.

That would be very welcome! You can find the sources at
github.com/LINBIT/linbit-documentation (out of my head, something like
that). It contains a README, but the short version is:

- get asciidoctor
- cd UG9
- rewrite
- make html
- find the output in output-html

Thanks, rck



More information about the drbd-user mailing list