CLOSE (was RE: Swapfd error)

[Kenneth Brody]

Quoting Lerebours, Jose (Thu, 11 May 2006 15:08:34 -0500):

> In shock Ken wondered:
>
> >
> > Quoting Lerebours, Jose (Thu, 11 May 2006 14:41:46 -0500):
> > [...]
> > > Be careful with using 'close' too many times ... I've found
> > > it to cause the now non-existing "Segmentation Violation"
> >
> > Huh?
> >
>
> Well, nothing I can prove 110% of the times but in occasions
> where I encountered said error, removing the 'close' and/or
> 'write' commands made the errors go away.
>
> Of course, this is not to say the these commands were the true
> cause of the error but the commands that triggered the error.

Well, there was a problem (only recently reported, and since then
fixed) where a "CLOSE lookupname" followed by "WRITE lookupname"
(as opposed to WRITE followed by CLOSE) could cause such a crash.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com