Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!sdd.hp.com!hplabs!hpfcso!hpfcdc!koren
From: koren@hpfcdc.HP.COM (Steve Koren)
Newsgroups: comp.sys.amiga.misc
Subject: Re: SKsh and A3000
Message-ID: <37090002@hpfcdc.HP.COM>
Date: 7 Feb 91 16:31:00 GMT
References: <1991Jan31.232429.25396@max.physics.sunysb.edu>
Organization: HP Fort Collins, Co.
Lines: 15

Kent Polk writes:

> I was the one who discovered the method of placing a lock on

> Unfortunately, I don't know about the inner workings of this stuff & so
> don't have too many easy suggestions. If anyone can shed some light on
> this matter, I sure would appreciate it.

That is mighty strange.  The only thing I can think of which would be
affected by an existing lock is the code which opens .skshinit for
reading.  Its pretty normal code, though - just uses Open() to open
the file and get a file handle.  I'll look at it tonight and see if I
can see something strange with it.

   - steve