1998/02/17 10:47:38| Detected DEAD Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:38| Detected REVIVED Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:38| Detected DEAD Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:39| Detected REVIVED Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:39| Detected DEAD Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:39| Detected REVIVED Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:39| Detected DEAD Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:39| Detected REVIVED Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:39| Detected DEAD Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:39| Detected REVIVED Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:40| Detected DEAD Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:40| Detected REVIVED Sibling: 203.12.221.99/80/3130
1998/02/17 10:47:40| Detected DEAD Sibling: 203.12.221.99/80/3130
On and on and on and on.
Hmm. This looks like it would cure the problem. Not certain that it's
the correct logic tho...
--- n.c.old Tue Feb 17 10:49:11 1998
+++ neighbors.c Tue Feb 17 10:49:29 1998
@@ -520,7 +520,7 @@
{
int rtt;
int n;
- if (p->stats.logged_state == PEER_DEAD) {
+ if (p->stats.logged_state == PEER_DEAD && p->tcp_up) {
debug(15, 0) ("Detected REVIVED %s: %s/%d/%d\n",
neighborTypeStr(p),
p->host, p->http_port, p->icp_port);
Received on Tue Jul 29 2003 - 13:15:46 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:11:43 MST