On Fri, 11 Dec 2015, Donald Sharp wrote:
From: Vipin Kumar <[email protected]>
If on-shutdown is configured to a large value and 'service quagga
restart' is executed, then the init.d/quagga script doesnt wait more
than 120 seconds for the daemon do stop, worse, it goes ahead and
starts the new daemon regardless.
Is this appropriate for Quagga upstream?
(resend of):
# this seems like a hack? Does this occur with more intelligent init
# systems?
diff --git a/ospfd/ospf_vty.c b/ospfd/ospf_vty.c
index b05f07b..2064d48 100644
--- a/ospfd/ospf_vty.c
+++ b/ospfd/ospf_vty.c
@@ -6580,7 +6580,7 @@ DEFUN (no_ospf_max_metric_router_lsa_startup,
DEFUN (ospf_max_metric_router_lsa_shutdown,
ospf_max_metric_router_lsa_shutdown_cmd,
- "max-metric router-lsa on-shutdown <5-86400>",
+ "max-metric router-lsa on-shutdown <5-100>",
"OSPF maximum / infinite-distance metric\n"
"Advertise own Router-LSA with infinite distance (stub router)\n"
"Advertise stub-router prior to full shutdown of OSPF\n"
--
Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
Bounders get bound when they are caught bounding.
-- Ralph Lewin
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
