This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag


About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2019-12-12 10:42:16

Zasady formatowania tekstu

Pozostaw puste linie pomiędzy akapitami. Użyj [[BR]] żeby wstawić łamanie linii wewnątrz akapitu.

You can render text in italics or bold. To write italics, enclose the text in double single quotes. To write bold, enclose the text in triple single quotes. Underlined text needs a double underscore on each side. You get superscripted text by enclosing it into caret characters, and subscripts have to be embedded into double commas. If you need something smaller or larger you can get that by writing ~-smaller-~ or ~+larger+~.

Możesz wstawiać tekst pochylony lub wytłuszczony. Pochylenie uskasz poprzez otoczenie tekstu ''podwójnymi apostrofami''. Wytłuszczenie uzyskasz poprzez otoczenie tekstu '''potrójnymi apostrofami'''. Podkreślony tekst wymaga dwóch znaków podkreślenia po obydwu stronach. Można uzyskać indeks górny, otaczając go znakami "daszka": ^, natomiast indeks dolny powinien być otoczony dwoma przecinkami po każdej stronie. Jeżeli potrzebujesz napisać fragment tekstu mniejszą lub większą czcionką, możesz uzykać to pisząc ~-mniejsze-~ lub ~+większe+~.

Żeby wstawić kod proramu czcionką o stałej szerokości bez przetwarzania formatowania, użyj trzech nawiasów klamrowych:

10 PRINT "Witaj świecie!"
20 GOTO 10

Note that within code sections, both inline and display ones, any wiki markup is ignored. An alternative and shorter syntax for inlined code is to use backtick characters (note that this can be disabled by the site's configuration, but is enabled by default).

For more information on the possible markup, see HelpOnEditing.


__Mixing__ ''italics'' and '''bold''':
 * '''''Mix''' at the beginning''
 * '''''Mix'' at the beginning'''
 * '''Mix at the ''end'''''
 * ''Mix at the '''end'''''

You might recall ''a''^2^ `+` ''b''^2^ `=` ''c''^2^ from your math lessons, unless your head is filled with H,,2,,O.

An { { {inline code sequence} } } has the start and end markers on the same line. Or you use `backticks`.

A code display has them on different lines: { { {
'''No''' markup here!
} } }

/!\ In the above example, we "escaped" the markers for source code sequences by inserting spaces between the curly braces.


Mixing italics and bold:

  • Mix at the beginning

  • Mix at the beginning

  • Mix at the end

  • Mix at the end

You might recall a2 + b2 = c2 from your math lessons, unless your head is filled with H2O.

An inline code sequence has the start and end markers on the same line. Or you use backticks.

A code display has them on different lines:

'''No''' markup here!

Colorized code displays

There are several ways to get colorized formatting of code1:

  1. start a code display with a line only containing "#!PARSERNAME"
  2. embed a file attachment bearing a ".py" extension via "inline:"
  3. start a page with a format processing instruction ("#format PARSERNAME")


   1 from colors import palette
   2 palette.colorize('python')
  • 1 There is currently only support for limited number of languages, see HelpOnParsers.