Hmm. Not seen _this_ one before

Here's a new one on me:
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter
98/01/21 13:06:13| WARNING: bad ck_conn_event_pend counter

The hub router is offline doing unscheduled maintenance, so I ducked
in, changed err_html_text and SIGHUPed the proxy. It spat all these just
after reconfiguring.

D

--
Did you read the documentation AND the FAQ?
If not, I'll probably still answer your question, but my patience will
be limited, and you take the risk of sarcasm and ridicule.