From owner-freebsd-questions  Sat Apr  5 12:32:33 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA26224
          for questions-outgoing; Sat, 5 Apr 1997 12:32:33 -0800 (PST)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA26219
          for <questions@FreeBSD.ORG>; Sat, 5 Apr 1997 12:32:32 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id MAA05958; Sat, 5 Apr 1997 12:32:27 -0800 (PST)
Date: Sat, 5 Apr 1997 12:32:27 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Frank Seltzer <frankd@yoda.fdt.net>
cc: Dave Hummel <HUMMDN36@buffalostate.edu>, questions@FreeBSD.ORG
Subject: Re: Minicom caused crash
In-Reply-To: <Pine.BSF.3.96.970405073634.29519B-100000@Kryten.nina.org>
Message-ID: <Pine.BSF.3.96.970405123155.5894H-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 5 Apr 1997, Frank Seltzer wrote:

> > 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.

That too.  I'm used to Seyon (I think) giving me device busy errors, and
it's related to the device permissions.  Thanks for the info tho.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major