From owner-freebsd-isdn Fri May 29 05:50:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24052 for freebsd-isdn-outgoing; Fri, 29 May 1998 05:50:35 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24019 for ; Fri, 29 May 1998 05:50:31 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA17346 for ; Fri, 29 May 1998 12:50:30 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA26276; Fri, 29 May 1998 14:50:16 +0200 (MET DST) Message-ID: <19980529144855.61889@follo.net> Date: Fri, 29 May 1998 14:48:55 +0200 From: Eivind Eklund To: freebsd-isdn@FreeBSD.ORG Subject: _Strange_ output from isdntrace Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was running a trace on a 'normal' ISDN line (one I just rent from the telco) when this suddenly happened: # isdntrace =========== isdntrace controller #0 =========== started Fri May 29 12:41:55 1998 ccÂccgcccQ # I think the trace stood for about two hours before spitting out this and exitting. I noticed at 'Fri May 29 14:43:21 1998' minus the time of typing 'isdntrace' :-) Upon noticing, I immediately restarted isdntrace under a 'time' - so we'll get data on whether it quit in two hours again :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message