Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Apr 1997 12:32:27 -0800 (PST)
From:      Doug White <dwhite@gdi.uoregon.edu>
To:        Frank Seltzer <frankd@yoda.fdt.net>
Cc:        Dave Hummel <HUMMDN36@buffalostate.edu>, questions@FreeBSD.ORG
Subject:   Re: Minicom caused crash
Message-ID:  <Pine.BSF.3.96.970405123155.5894H-100000@localhost>
In-Reply-To: <Pine.BSF.3.96.970405073634.29519B-100000@Kryten.nina.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970405123155.5894H-100000>