fsnotify usage

[nncp.git] / doc / call.texi

diff --git a/doc/call.texi b/doc/call.texi
index fe55de5456d2b9f82c4aa83b428f6c13155d4c0b..52572baa11558f2a9a62a94a3d496a14510b5572 100644 (file)
--- a/doc/call.texi
+++ b/doc/call.texi
@@ -1,7 +1,7 @@
 @node Call
 @unnumbered Call configuration
 
-Call is a rule when and how node can be called.
+Call is a rule when and how node can be called by @ref{nncp-caller}.
 
 Example list of call structures:
 
@@ -14,7 +14,7 @@ calls: [
 
         autotoss: true
         autotoss-doseen: true
-    },
+    }
     {
         cron: "30 * * * SAT,SUN"
         onlinedeadline: 1800
@@ -22,17 +22,18 @@ calls: [
         nice: NORMAL
         rxrate: 10
         txrate: 20
-    },
+    }
     {
         cron: "0 * * * SAT,SUN"
         xx: rx
         addr: lan
-    },
+    }
     {
         cron: "*/5 * * * * * *"
         when-tx-exists: true
         nock: true
-    },
+        mcd-ignore: true
+    }
 ]
 @end verbatim
 
@@ -84,7 +85,11 @@ during the call. You can control either are @file{.seen} files must be
 created, or skip any kind of packet processing.
 
 @item when-tx-exists
-Call only if packets for sending exists.
+Call only if packets for sending exists. The check of outbound packets
+existence is performed @strong{every} time we are going to make a call,
+but @emph{when-tx-exists} does not influence @emph{cron}. When
+@emph{cron} configuration decides that it is time to make a call, with
+@emph{when-tx-exists} option it checks packets existence first.
 
 @anchor{CfgNoCK}
 @item nock
@@ -96,4 +101,9 @@ received one, but just sequential writing of the file. Pay attention
 that you have to make a call to remote node after checksumming is done,
 to send notification about successful packet reception.
 
+@anchor{CfgMCDIgnore}
+@item mcd-ignore
+Ignore @ref{MCD} announcements: do not add MCD addresses for possible
+connection attempts.
+
 @end table