From owner-freebsd-isdn Fri Oct 2 05:25:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16136 for freebsd-isdn-outgoing; Fri, 2 Oct 1998 05:25:09 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16117 for ; Fri, 2 Oct 1998 05:25:02 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id ITRDNNSK; Fri, 02 Oct 98 12:24:42 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981002141949.00952770@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 02 Oct 1998 14:19:49 +0200 To: "Hallam Oaks P/L list account" From: Marius Bendiksen Subject: Re: i4b reset ? Cc: freebsd-isdn@FreeBSD.ORG In-Reply-To: <199810021128.VAA28987@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >apparently indefinately, even though the controlling process has been killed. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is actually the most annoying part. If it'd just quit spewing out errors once you'd shut everything down, things'd be a lot more cool. >Is there any simple way to reset the entire i4b subsystem to the state in >which it was when the system first booted (or close enough to it) ? >Currently I'm just rebooting but that's getting tiresome :( Indeed. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message