summaryrefslogtreecommitdiff
path: root/proto/static/static.c
diff options
context:
space:
mode:
authorMartin Mares <mj@ucw.cz>2000-06-08 12:37:21 +0000
committerMartin Mares <mj@ucw.cz>2000-06-08 12:37:21 +0000
commit725270cb1da0672128675924844531e56c6ea64e (patch)
tree06fcfcd87498d35138a888719a35128df1ed8438 /proto/static/static.c
parent8d56febe64769c19a06c2c0f3ff121d25eceaa5b (diff)
Fixes for the programmer's manual.
Diffstat (limited to 'proto/static/static.c')
-rw-r--r--proto/static/static.c13
1 files changed, 6 insertions, 7 deletions
diff --git a/proto/static/static.c b/proto/static/static.c
index beb5a1b9..eb6c1c11 100644
--- a/proto/static/static.c
+++ b/proto/static/static.c
@@ -9,19 +9,18 @@
/**
* DOC: Static
*
- * The Static protocol is implemented in a very straightforward way. It keeps
- * a two lists of static routes: one containing interface routes and one
+ * The Static protocol is implemented in a straightforward way. It keeps
+ * two lists of static routes: one containing interface routes and one
* holding the remaining ones. Interface routes are inserted and removed according
- * to interface events received from the core via the if_notify() hook, routes
+ * to interface events received from the core via the if_notify() hook. Routes
* pointing to a neighboring router use a sticky node in the neighbor cache
- * to be notified about gaining or losing the neighbor and finally special
+ * to be notified about gaining or losing the neighbor. Special
* routes like black holes or rejects are inserted all the time.
*
* The only other thing worth mentioning is that when asked for reconfiguration,
* Static not only compares the two configurations, but it also calculates
- * difference between the lists of static routes mentioned in the old config
- * and the lists in the new one and it just inserts the newly added routes
- * and removes the obsolete ones.
+ * difference between the lists of static routes and it just inserts the
+ * newly added routes and removes the obsolete ones.
*/
#undef LOCAL_DEBUG