Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!SRI-NIC.ARPA!tcp-ip-RELAY From: tcp-ip-RELAY@SRI-NIC.ARPA Newsgroups: comp.protocols.tcp-ip Subject: (none) Message-ID: <8901141330.AA23970@ucbvax.Berkeley.EDU> Date: 14 Jan 89 13:30:58 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 42 HELO ADMIN.BYU.EDU TICK 1925 MAIL FROM: RCPT TO: DATA Received: by BYUADMIN (Mailer R2.01A) id 1925; Fri, 13 Jan 89 19:33:10 MST Date: Fri, 13 Jan 89 15:13:40 GMT Reply-To: Sender: "(TCP-IP ARPA Discussions)" Comments: Warning -- original Sender: tag was tcp-ip-relay@SRI-NIC.ARPA From: Brian Kantor Subject: dda0: Call Cleared LCN x cause code 9 diag code 88 To: "WCC Participate Redistribution (U Iowa)" Environment: Vax780, ACC6250 interface, X.25 connection to PSN 26.5.0.3 "dda0: Call Cleared LCN x cause code 9 diag code 88" Ever since the new PSN software was installed on our Milnet IMP, we've been getting thousands of these messages, often several a minute. From what I can see, they are not an error, but instead represent a change in the PSN software that now advises me that a host is down by blowing the X.25 connection out of the water instead of just letting it time out. The difficulty is that each and every one of these cleared calls causes a message to get printed on the console, and we're wasting trees. I've ADB-hotpatched a null into the beginning of the print string in the system kernel to stop the messages, and perhaps at some later time I'll take the printf out or modify the conditions under which it squirts out. Any insight or advice on this? Am I doing the right thing by ignoring and suppressing these messages, or is there really something wrong? Brian Kantor UCSD Office of Academic Computing Academic Network Operations Group UCSD B-028, La Jolla, CA 92093 USA brian@ucsd.edu ucsd!brian BRIAN@UCSD . QUIT