Since now I can also use 'dead interval', not just 'dead counter'.

1 files changed, 7 insertions, 0 deletions

diff --git a/doc/bird.sgml b/doc/bird.sgml
index 79d7e96..3c23309 100644
--- a/doc/bird.sgml
+++ b/doc/bird.sgml
@@ -1024,6 +1024,7 @@ protocol ospf <name> {
 			priority <num>;
 			wait <num>;
 			dead count <num>;
+			dead <num>;
 			type [broadcast|nonbroadcast|pointopoint];
 			strict nonbroadcast <switch>;
 			authentication [none|simple];
@@ -1048,6 +1049,7 @@ protocol ospf <name> {
 			retransmit <num>;
 			wait <num>;
 			dead count <num>;
+			dead <num>;
 			authentication [none|simple];
 			password "<text>";
 		};
@@ -1126,6 +1128,11 @@ protocol ospf <name> {
 	 When the router does not receive any messages from a neighbor in
 	 <m/dead count/*<m/hello/ seconds, it will consider the neighbor down.
 
+	<tag>dead <M>num</M></tag>
+	 When the router does not receive any messages from a neighbor in
+	 <m/dead/ seconds, it will consider the neighbor down. If both directives
+	 <m/dead count/ and <m/dead/ are used, <m/dead/ has precendence.
+
 	<tag>type broadcast</tag>
 	 BIRD detects a type of a connected network automatically, but sometimes it's
 	 convenient to force use of a different type manually.