From owner-freebsd-questions Sat Apr 5 04:52:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA06031 for questions-outgoing; Sat, 5 Apr 1997 04:52:24 -0800 (PST) Received: from yoda.fdt.net (root@yoda.fdt.net [205.229.48.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA06024 for ; Sat, 5 Apr 1997 04:52:20 -0800 (PST) Received: from Kryten.nina.org (port-73.ts1.gnv.fdt.net [205.229.51.73]) by yoda.fdt.net with SMTP id HAA18329; Sat, 5 Apr 1997 07:39:07 -0500 Date: Sat, 5 Apr 1997 07:39:04 -0500 (EST) From: Frank Seltzer X-Sender: frankd@Kryten.nina.org To: Doug White cc: Dave Hummel , questions@FreeBSD.ORG Subject: Re: Minicom caused crash In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 4 Apr 1997, Doug White wrote: > On Fri, 4 Apr 1997, Dave Hummel wrote: > > > This is actually the second time this has happened. Minicom caused a reboot > > when starting up. I wasn't paying enought attention to see if it happened during > > modem initialization, but I have a feeling it did. Now I also get "Device > > /dev/modem locked" errors in Kermit and Minicom. My modem performs nicely under > > dos kermit and ijjppp. Any ideas on what may have caused this? Also, how to > > unlock modem? > > Make sure the permissions are ok on the device. Make sure your user is a > member of group 'dialer'. Doug, Good suggestions but I think the problem is that Dave has a stale lock file in /var/spool/lock that won't let him access the modem. If minicom crashed, it probably did not delete the lock file. > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > Frank -- Only in America can a homeless veteran sleep in a cardboard box while a draft dodger sleeps in the White House - anonymous